Re: [RFC] Splitting kernel headers and deprecating __KERNEL__

[Linus Torvalds]

On Tue, 30 Nov 2004, David Howells wrote:
> 
> If you did user annotations you'd have to solve the problem of applying it to
> #defines and still allowing the constants to be used in assembly. Obviously
> this is not impossible. This is trivial with __KERNEL__ or separation into
> other files.

Annotations don't have to be per-entry. It can be something as simple as 
"this particular file is exposed to user space", or "things from here to 
here are exposed to user space".

And while automation is good, sometimes automation isn't even worth it. I 
suspect it might be good just to _comment_ the structures we expose to 
user space, even if it's never used for anything but as a note to tell 
people not to change it.

		Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/