On Sat, Apr 22, 2006 at 01:03:03PM +0100, David Woodhouse wrote:
> On Sat, 2006-04-22 at 11:33 +0200, Adrian Bunk wrote:
>...
> Ideally, I'd like to proceed by splitting files into user-visible and
> kernel-private parts in _separate_ headers, so that the 'unifdef' part
> becomes unnecessary (and __KERNEL__ disappears entirely). I've done some
> of that already in include/mtd). It would also be nice if we could then
> put the user-visible files into a separate directory, so that the
> 'headers_export' step becomes nothing more than a 'cp -a'. We do need to
> do this incrementally though, and I think this is going to be the best
> way to do it, and to get it accepted.
This sounds like what I had in mind.
> > Unless someone can tell me a reason why this wouldn't work (except for
> > being a bit more work than your approach), this is the approach I have
> > in mind for working on.
>
> Your approach is basically what we proposed at last year's Kernel
> Summit. It was shot down though, so we're trying to start simple and do
> it incrementally.
What was the recommended way for getting userspace header at last year's
kernel summit?
> The important thing is that we all get our editors out and clean up the
> _contents_ our own headers, and actually start to _think_ about the
> visibility of any new header-file content we introduce. Let's not
> concentrate too much on the implementation details of how we actually
> get those to userspace.
Currently, it's said the kernel headers aren't suitable for userspace.
After the cleanups you propose, the kernel headers will be suitable for
userspace (the copy steps you propose are not required, distributions
could equally start to copy the verbatim headers again).
If everyone is working in a different direction, this is only wasting
work.
> dwmw2
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
