From: David Vrabel <dvrabel@arcom.com>
To: David Woodhouse <dwmw2@infradead.org>
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 12:52:28 +0100 [thread overview]
Message-ID: <4176517C.4090504@arcom.com> (raw)
In-Reply-To: <1098268885.3872.81.camel@baythorne.infradead.org>
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?
> It should use standard types (like uint16_t etc)
Why doesn't the kernel use these standard types also?
David Vrabel
--
David Vrabel, Design Engineer
Arcom, Clifton Road Tel: +44 (0)1223 411200 ext. 3233
Cambridge CB1 7EA, UK Web: http://www.arcom.com/
next prev parent reply other threads:[~2004-10-20 11:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 20:59 [LARTC] [ANNOUNCE] iproute2 2.6.9-041019 Stephen Hemminger
2004-10-19 20:59 ` Stephen Hemminger
2004-10-20 0:21 ` Jeff Chua
2004-10-20 7:00 ` [LARTC] " Harald Welte
2004-10-20 7:00 ` Harald Welte
2004-10-20 9:41 ` [LARTC] iproute2 and 2.6.9 kernel headers (was Re: [ANNOUNCE] iproute2 2.6.9-041019) Harald Welte
2004-10-20 9:41 ` Harald Welte
2004-10-20 10:41 ` David Woodhouse
2004-10-20 11:52 ` David Vrabel [this message]
2004-10-20 12:19 ` David Woodhouse
2004-10-20 16:15 ` [LARTC] Re: [ANNOUNCE] iproute2 2.6.9-041019 Stephen Hemminger
2004-10-20 16:15 ` Stephen Hemminger
2004-10-21 2:53 ` Jeff Chua
2004-10-20 16:18 ` [LARTC] " Stephen Hemminger
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=4176517C.4090504@arcom.com \
--to=dvrabel@arcom.com \
--cc=LARTC@mailman.ds9a.nl \
--cc=dwmw2@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.