From: David Woodhouse <dwmw2@infradead.org>
To: Stefan Rompf <stefan@loplof.de>
Cc: Thomas Graf <tgraf@suug.ch>, David Miller <davem@davemloft.net>,
drow@false.org, joseph@codesourcery.com, netdev@vger.kernel.org,
libc-alpha@sourceware.org, akpm@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [NETLINK]: Schedule removal of old macros exported to userspace
Date: Tue, 12 Dec 2006 11:23:51 +0000 [thread overview]
Message-ID: <1165922631.5253.623.camel@pmac.infradead.org> (raw)
In-Reply-To: <200612091559.05232.stefan@loplof.de>
On Sat, 2006-12-09 at 15:58 +0100, Stefan Rompf wrote:
> But when even glibc needs internal compat headers to compile with the second
> kernel version that provides userspace headers, what is the long-term - even
> mid-term - perspective of make headers_install then?
Bear in mind that with the first cut of the headers_install I was trying
to keep it entirely uncontentious and stick to _mechanism_, not policy.
The _first_ set of exported headers still aren't ideal, and we're still
cleaning up some parts of them (like properly getting rid of the
_syscallX() macros, etc.).
We've only just started to be sensible about what we export to userspace
-- it's not entirely set in stone at this point,
--
dwmw2
next prev parent reply other threads:[~2006-12-12 11:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061208.134752.131916271.davem@davemloft.net>
[not found] ` <20061208.171455.11932070.davem@davemloft.net>
[not found] ` <20061209103953.GN8693@postel.suug.ch>
2006-12-09 11:49 ` Stefan Rompf
2006-12-09 12:55 ` Thomas Graf
2006-12-09 14:58 ` Stefan Rompf
2006-12-09 21:50 ` David Miller
2006-12-09 22:02 ` David Woodhouse
2006-12-12 11:23 ` David Woodhouse [this message]
2006-12-09 21:49 ` 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=1165922631.5253.623.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=drow@false.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stefan@loplof.de \
--cc=tgraf@suug.ch \
/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®