All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Brad Hards <bhards@bigpond.net.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Header files and the kernel ABI
Date: Thu, 25 Jul 2002 09:17:40 -0700	[thread overview]
Message-ID: <3D4024A4.5090806@zytor.com> (raw)
In-Reply-To: 200207252308.00656.bhards@bigpond.net.au

Brad Hards wrote:
> 
> I like it (having just argued for it), except for the __s* and __u*.
> The ABI definitions aren't for kernel programmers. They are for 
> userspace programmers. So we should use standard types,
> even if they are a bit ugly (and uint16_t isn't really much uglier
> than __u16, and at least it doesn't carry connotations of
> something that is meant to be internal, which is what the standard
> double-underscore convention means). 
> 

Not quite -- it means they are implementation-specific (in this case, 
Linux-specific.)  The Linux __s* and __u* predates <stdint.h>; I 
certainly would like to migrate to <stdint.h> but I don't see it as a 
very high priority.

	-hpa



  parent reply	other threads:[~2002-07-25 16:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-25  6:28 Header files and the kernel ABI H. Peter Anvin
2002-07-25  6:51 ` Andreas Dilger
2002-07-25  7:07   ` H. Peter Anvin
2002-07-25  7:32     ` Andreas Dilger
2002-07-25 16:29       ` Oliver Xymoron
2002-07-25 16:31         ` H. Peter Anvin
2002-07-25 18:19           ` Erik Andersen
2002-07-25 20:03             ` Oliver Xymoron
2002-07-27 11:29               ` Eric W. Biederman
2002-07-25 16:30       ` H. Peter Anvin
2002-07-25  8:00 ` DervishD
2002-07-25 13:08 ` Brad Hards
2002-07-25 16:09   ` DervishD
2002-07-25 16:17   ` H. Peter Anvin [this message]
2002-07-25 18:22     ` Erik Andersen
2002-07-31 21:37 ` Kernel ABI BoF at Linux-Kongress? [was: Header files and the kernel ABI] Brad Hards
  -- strict thread matches above, loose matches on Subject: below --
2002-07-25 21:13 Header files and the kernel ABI dank
2002-07-26  2:37 ` jw schultz

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=3D4024A4.5090806@zytor.com \
    --to=hpa@zytor.com \
    --cc=bhards@bigpond.net.au \
    --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 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.