From: Adrian Bunk <bunk@stusta.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel@vger.kernel.org, sam@ravnborg.org
Subject: Re: [PATCH] 'make headers_install' kbuild target.
Date: Sat, 22 Apr 2006 16:11:34 +0200 [thread overview]
Message-ID: <20060422141134.GC5010@stusta.de> (raw)
In-Reply-To: <1145712964.11909.258.camel@pmac.infradead.org>
On Sat, Apr 22, 2006 at 02:36:04PM +0100, David Woodhouse wrote:
> On Sat, 2006-04-22 at 15:20 +0200, Adrian Bunk wrote:
>...
> > Assume you have a header include/linux/foo.h:
> > - Add an #include <kabi/linux/foo.h> at the top.
> > - Move the part of the contents that is part of the userspace ABI to
> > include/kabi/linux/foo.h.
>
> Absolutely. That's what I've done with MTD headers already, although the
> directory names are different. The directory names don't _matter_
> either, because important part was that the files themselves are cleaned
> up.
>
> Linus isn't keen on splitting it into a new directory, and I don't want
> to start off by demanding that. As I said, the important part of the
> above is the bit where one of us goes to the file with an editor and
> identifies the public parts vs. the private parts, then splits them up
> -- possibly with #ifdef __KERNEL__, but _preferably_ into separate
> files. And it doesn't _matter_ which directories we put those files
> into, for now. I don't want to talk about it _yet_ because it's just
> taking attention away from the real problem.
>
> The more we screw around with such minutiae, the less likely we are to
> get traction with Linus -- despite the fact that almost everyone who's
> expressed an opinion is _agreeing_ with you about where we want to end
> up.
>
> We need to keep it simple and unintrusive to start with. Concentrate on
> the _contents_ and then we can deal with the less important details
> later.
Sorry, but I'm not a fan of doing much more work than required instead
of getting a consensus first and then implementing the solution.
Let's agree on the way to go first, give me two weeks, and I can submit
a first batch of the header splitting that will both not break any
kernel code and be enough for compiling most of the userspace.
Perhaps two weeks are too optimistic for some parts considering the
state of our headers, but getting it done before OLS seems realistic.
But otherwise, I think I have better things to do in the part of my
spare time I'm devoting to Linux kernel development.
> 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
next prev parent reply other threads:[~2006-04-22 19:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-22 2:17 [PATCH] 'make headers_install' kbuild target David Woodhouse
2006-04-22 9:33 ` Adrian Bunk
2006-04-22 12:03 ` David Woodhouse
2006-04-22 12:38 ` Adrian Bunk
2006-04-22 12:48 ` David Woodhouse
2006-04-22 13:20 ` Adrian Bunk
2006-04-22 13:36 ` David Woodhouse
2006-04-22 14:11 ` Adrian Bunk [this message]
2006-04-22 14:26 ` David Woodhouse
2006-04-22 14:44 ` Adrian Bunk
2006-04-22 14:56 ` David Woodhouse
2006-04-22 15:30 ` David Woodhouse
2006-04-22 21:13 ` Arnd Bergmann
2006-04-23 7:09 ` Arjan van de Ven
2006-04-23 16:51 ` Arnd Bergmann
2006-04-23 17:00 ` Joshua Hudson
2006-04-22 14:14 ` Sam Ravnborg
2006-04-22 14:20 ` Adrian Bunk
2006-04-22 14:28 ` Sam Ravnborg
2006-04-22 14:47 ` David Woodhouse
2006-04-22 14:50 ` Adrian Bunk
2006-04-28 18:15 ` Rob Landley
2006-04-28 18:27 ` David Woodhouse
2006-04-28 19:59 ` Rob Landley
2006-04-22 14:35 ` David Woodhouse
2006-04-23 20:47 ` David Woodhouse
2006-04-24 0:12 ` David Woodhouse
2006-04-28 18:13 ` Rob Landley
2006-04-28 18:22 ` David Woodhouse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060422141134.GC5010@stusta.de \
--to=bunk@stusta.de \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox