From: David Woodhouse <dwmw2@infradead.org>
To: David Vrabel <dvrabel@arcom.com>
Cc: Harald Welte <laforge@gnumonks.org>,
Jeff Chua <jeffchua@silk.corp.fedex.com>,
Stephen Hemminger <shemminger@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
netdev@oss.sgi.com, linux-net@vger.kernel.org,
LARTC@mailman.ds9a.nl
Subject: Re: iproute2 and 2.6.9 kernel headers (was Re: [ANNOUNCE] iproute2 2.6.9-041019)
Date: Wed, 20 Oct 2004 13:19:48 +0100 [thread overview]
Message-ID: <1098274788.3872.90.camel@baythorne.infradead.org> (raw)
In-Reply-To: <4176517C.4090504@arcom.com>
On Wed, 2004-10-20 at 12:52 +0100, David Vrabel wrote:
> David Woodhouse wrote:
> >
> > The time has come to fix it properly instead. Anything which these tools
> > actually need from the kernel headers should be moved into a separate
> > header file (still in the kernel source) which is usable from _both_
> > kernel and userspace.
>
> Isn't this what linux-libc-headers is for?
The separate linux-libc-headers is a hack, which will be able to die
once we properly clean up the kernel headers into those which are
'exported' and those which are private.
> > It should use standard types (like uint16_t etc)
>
> Why doesn't the kernel use these standard types also?
Archaic personal preference. Inside the kernel that's fair enough.
--
dwmw2
next prev parent reply other threads:[~2004-10-20 12:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 20:59 [ANNOUNCE] iproute2 2.6.9-041019 Stephen Hemminger
2004-10-20 0:21 ` Jeff Chua
2004-10-20 7:00 ` Harald Welte
2004-10-20 9:41 ` iproute2 and 2.6.9 kernel headers (was Re: [ANNOUNCE] iproute2 2.6.9-041019) Harald Welte
2004-10-20 10:41 ` David Woodhouse
2004-10-20 11:52 ` David Vrabel
2004-10-20 12:19 ` David Woodhouse [this message]
2004-10-20 16:15 ` [ANNOUNCE] iproute2 2.6.9-041019 Stephen Hemminger
2004-10-21 2:53 ` Jeff Chua
2004-10-20 16:18 ` Stephen Hemminger
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=1098274788.3872.90.camel@baythorne.infradead.org \
--to=dwmw2@infradead.org \
--cc=LARTC@mailman.ds9a.nl \
--cc=dvrabel@arcom.com \
--cc=jeffchua@silk.corp.fedex.com \
--cc=laforge@gnumonks.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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®