From: Erik Andersen <andersen@codepoet.org>
To: Matthew Wilcox <willy@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel header separation
Date: Fri, 5 Sep 2003 15:16:04 -0600 [thread overview]
Message-ID: <20030905211604.GB16993@codepoet.org> (raw)
In-Reply-To: <20030905144154.GL18654@parcelfarce.linux.theplanet.co.uk>
On Fri Sep 05, 2003 at 03:41:54PM +0100, Matthew Wilcox wrote:
> On Tue, Sep 02, 2003 at 07:49:09PM -0600, Erik Andersen wrote:
> > Header files intended for use by users should probably drop
> > linux/types.h just include <stdint.h>,,, Then convert the
> > types over to ISO C99 types.
>
> stdint.h is a userspace header. I suppose we could clone it for the
> kernel, but I don't see any need to.
>
> > s/__u8/uint8_t/g
> > s/__u16/uint16_t/g
> > s/__u32/uint32_t/g
> > s/__u64/uint64_t/g
>
> i think all these _t types are ugly ;-(
They may be ugly, but they are standardized and have very
precise meanings defined by ISO C99, which is a very good
thing for code interoperability...
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
next prev parent reply other threads:[~2003-09-05 21:16 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 [this message]
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
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=20030905211604.GB16993@codepoet.org \
--to=andersen@codepoet.org \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@debian.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