From: Matthew Wilcox <willy@debian.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
David Woodhouse <dwmw2@infradead.org>,
Matthew Wilcox <willy@debian.org>,
Erik Andersen <andersen@codepoet.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel header separation
Date: Mon, 8 Sep 2003 15:42:32 +0100 [thread overview]
Message-ID: <20030908144232.GP18654@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20030908143249.GA4462@gtf.org>
On Mon, Sep 08, 2003 at 10:32:49AM -0400, Jeff Garzik wrote:
> On Mon, Sep 08, 2003 at 10:25:45AM -0400, Jeff Garzik wrote:
> > Whenever I see "__u8", I think "non-standard, gcc-specific dependency"
>
> Ignore this, I stand corrected: these are kernel types.
>
> Regardless, I still prefer the C99 size-specific types, as they are the
> most portable across all compilers, and you can depend on the compiler
> to provide them for you. No need to define them yourself.
bzzt. glibc provides them, not gcc.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-09-08 14:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 19:16 kernel header separation Matthew Wilcox
2003-09-03 1:49 ` Erik Andersen
2003-09-05 14:36 ` David Woodhouse
2003-09-05 21:10 ` Erik Andersen
2003-09-05 14:41 ` Matthew Wilcox
2003-09-05 21:16 ` Erik Andersen
2003-09-05 23:22 ` Matthew Wilcox
2003-09-08 13:38 ` David Woodhouse
2003-09-08 14:12 ` Alan Cox
2003-09-08 14:25 ` Jeff Garzik
2003-09-08 14:31 ` Alan Cox
2003-09-08 14:32 ` Jeff Garzik
2003-09-08 14:42 ` Matthew Wilcox [this message]
2003-09-08 15:22 ` Andreas Schwab
2003-09-08 14:37 ` Andreas Schwab
2003-09-08 20:23 ` David Garfield
2003-09-08 20:34 ` Andries Brouwer
2003-09-08 21:05 ` David Garfield
2003-09-08 20:43 ` Erik Andersen
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=20030908144232.GP18654@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andersen@codepoet.org \
--cc=dwmw2@infradead.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.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