From: Takashi Iwai <tiwai@suse.de>
To: arnd@arndb.de
Cc: hpa@zytor.com, mingo@redhat.com, dwmw2@infradead.org,
acme@ghostprotocols.net, airlied@linux.ie, perex@perex.cz,
yoshfuji@linux-ipv6.org, mchehab@redhat.com, tglx@linutronix.de,
hpa@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [tip:core/header-fixes] make exported headers use strict posix types
Date: Thu, 26 Feb 2009 09:49:15 +0100 [thread overview]
Message-ID: <s5h3ae1k2gk.wl%tiwai@suse.de> (raw)
In-Reply-To: <tip-c0264157bba0cafd9265f30d846553161c0477b3@kernel.org>
At Thu, 26 Feb 2009 01:30:53 GMT,
Arnd Bergmann wrote:
>
> Author: Arnd Bergmann <arnd@arndb.de>
> AuthorDate: Thu, 26 Feb 2009 00:51:39 +0100
> Commit: H. Peter Anvin <hpa@linux.intel.com>
> CommitDate: Wed, 25 Feb 2009 17:27:59 -0800
>
> make exported headers use strict posix types
>
> A number of standard posix types are used in exported headers, which
> is not allowed if __STRICT_KERNEL_NAMES is defined. In order to
> get rid of the non-__STRICT_KERNEL_NAMES part and to make sane headers
> the default, we have to change them all to safe types.
>
> There are also still some leftovers in reiserfs_fs.h, elfcore.h
> and coda.h, but these files have not compiled in user space for
> a long time.
>
> This leaves out the various integer types ({u_,u,}int{8,16,32,64}_t),
> which we take care of separately.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Acked-by: Mauro Carvalho Chehab <mchehab@redhat.com>
> Cc: David Airlie <airlied@linux.ie>
> Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
> Cc: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
> Cc: netdev@vger.kernel.org
> Cc: linux-ppp@vger.kernel.org
> Cc: Jaroslav Kysela <perex@perex.cz>
> Cc: Takashi Iwai <tiwai@suse.de>
My ack for include/sound/asound.h,
Acked-by: Takashi Iwai <tiwai@suse.de>
thanks,
Takashi
parent reply other threads:[~2009-02-26 8:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <tip-c0264157bba0cafd9265f30d846553161c0477b3@kernel.org>]
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=s5h3ae1k2gk.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=acme@ghostprotocols.net \
--cc=airlied@linux.ie \
--cc=arnd@arndb.de \
--cc=dwmw2@infradead.org \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=mingo@redhat.com \
--cc=perex@perex.cz \
--cc=tglx@linutronix.de \
--cc=yoshfuji@linux-ipv6.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
all inboxes | Powered by JetHome®