From: David Woodhouse <dwmw2@infradead.org>
To: Jim Gifford <maillist@jg555.com>
Cc: David Miller <davem@davemloft.net>,
arjan@infradead.org, linux-kernel@vger.kernel.org,
ralf@linux-mips.org
Subject: Re: 2.6.18 Headers - Long
Date: Sat, 15 Jul 2006 08:19:42 +0100 [thread overview]
Message-ID: <1152947982.3191.116.camel@pmac.infradead.org> (raw)
In-Reply-To: <44B80543.4050608@jg555.com>
On Fri, 2006-07-14 at 13:57 -0700, Jim Gifford wrote:
> Do we have a list of what headers are "user-space" and which ones should
> not be "user-space"?
Well, we have the lists in include/*/Kbuild files, of course -- but
that's all. As I've stated before, I've been somewhat liberal with the
exports to far, to match what's currently (ab)used, because I wanted to
concentrate on the _mechanism_, not the policy.
The intention is that we can now start to tighten it up -- I've already
sent the patches which drop asm/atomic.h and asm/io.h, and there are
more which should go. Next on that list (and already commented as such
in include/asm-generic/Kbuild.asm) are asm/page.h and asm/elf.h.
> Also David W, let me know what I can do to help you out, a lot of people
> on my end want to get this working properly.
Thanks. One thing you can do which would be extremely useful is to
investigate dropping page.h and elf.h, and make sure that stuff like gdb
(and anything using ptrace.h) will still build. Then just look for
anything else which should be removed from view. The git repository at
http://git.kernel.org/git/?p=linux/kernel/git/dwmw2/kernel-headers.git
(git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/kernel-headers.git)
should help with that task. Provide patches to move stuff within #ifdef
__KERNEL__ or to move it to unexported files.
There are some who think that it would be nice to get rid of __KERNEL__
entirely -- files would be either entirely exported, or not at all. I
don't think we necessarily need to go that far; the export step with
unifdef isn't so bad.
--
dwmw2
next prev parent reply other threads:[~2006-07-15 7:20 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 0:35 Jim Gifford
2006-07-14 0:25 ` David Woodhouse
2006-07-14 2:18 ` Jim Gifford
2006-07-14 18:55 ` David Woodhouse
2006-07-14 19:28 ` Jim Gifford
2006-07-14 19:39 ` Arjan van de Ven
2006-07-14 20:16 ` David Woodhouse
2006-07-14 20:19 ` David Miller
2006-07-14 20:57 ` Jim Gifford
2006-07-15 4:33 ` Randy.Dunlap
2006-07-16 14:08 ` Nix
2006-07-15 7:19 ` David Woodhouse [this message]
2006-07-15 7:08 ` David Woodhouse
2006-07-14 19:57 ` David Woodhouse
2006-07-14 20:06 ` Erik Andersen
2006-07-14 20:19 ` Christoph Hellwig
2006-08-26 16:09 ` David Woodhouse
2006-08-29 12:25 ` Ralf Baechle
2006-07-15 21:09 Albert Cahalan
2006-07-15 21:19 ` Arjan van de Ven
2006-07-17 5:21 ` Ralf Baechle
2006-07-15 21:44 ` Adrian Bunk
2006-07-15 21:47 ` David Woodhouse
2006-07-16 6:18 ` Albert Cahalan
2006-07-16 6:26 ` Arjan van de Ven
2006-07-16 8:05 ` David Woodhouse
2006-07-16 8:20 ` Jakub Jelinek
2006-07-16 12:34 ` Kyle Moffett
2006-07-16 12:48 ` Russell King
2006-07-16 18:38 ` Albert Cahalan
2006-07-16 18:53 ` Russell King
2006-07-16 19:22 ` Albert Cahalan
2006-07-16 19:41 ` Russell King
2006-07-17 1:26 ` Arjan van de Ven
2006-07-17 1:23 ` David Miller
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=1152947982.3191.116.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=arjan@infradead.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maillist@jg555.com \
--cc=ralf@linux-mips.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
all inboxes | Powered by JetHome®