public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Sam Ravnborg <sam@ravnborg.org>,
	Kyle McMartin <kyle@infradead.org>, Ingo Molnar <mingo@elte.hu>,
	Jaswinder Singh Rajput <jaswinderrajput@gmail.com>,
	mingo@redhat.com, linux-kernel@vger.kernel.org,
	linux-arch@vger.kernel.org
Subject: Re: [PATCH] Make exported headers use strict posix types
Date: Thu, 26 Feb 2009 07:39:46 +0900	[thread overview]
Message-ID: <1235601586.4913.9.camel@macbook.infradead.org> (raw)
In-Reply-To: <49A5C118.3070605@zytor.com>

On Wed, 2009-02-25 at 14:07 -0800, H. Peter Anvin wrote:
> Arnd Bergmann wrote:
> > 
> > Actually, this change does belong in here: This is the only user of u_short
> > in exported headers, and nothing uses u_char, u_int or u_long, so it gets
> > rid of a whole class of types. The only questionable types left after this
> > are the standard stdint.h types, many of which are probably legitimate:
> > 
> 
> Not legitimate in *exported* headers.

Not in the ones which might be included implicitly by glibc, perhaps --
but other non-POSIX headers are perfectly entitled to require C standard
types, surely?

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@intel.com                              Intel Corporation

  reply	other threads:[~2009-02-25 22:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090225032553.GD6690@bombadil.infradead.org>
     [not found] ` <49A4F051.3000706@zytor.com>
     [not found]   ` <20090225072202.GI6690@bombadil.infradead.org>
2009-02-25 18:17     ` [PATCH] Make exported headers use strict posix types Arnd Bergmann
2009-02-25 20:11       ` Sam Ravnborg
2009-02-25 21:42         ` Arnd Bergmann
2009-02-25 21:58         ` Arnd Bergmann
2009-02-25 22:07           ` H. Peter Anvin
2009-02-25 22:39             ` David Woodhouse [this message]
2009-02-25 23:58               ` H. Peter Anvin
2009-02-25 23:07         ` H. Peter Anvin
2009-02-25 23:07           ` H. Peter Anvin
2009-02-26  0:01           ` Arnd Bergmann
2009-02-26  0:04             ` H. Peter Anvin

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=1235601586.4913.9.camel@macbook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=arnd@arndb.de \
    --cc=hpa@zytor.com \
    --cc=jaswinderrajput@gmail.com \
    --cc=kyle@infradead.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=sam@ravnborg.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