From: Sam Ravnborg <sam@ravnborg.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Kyle McMartin <kyle@infradead.org>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
Jaswinder Singh Rajput <jaswinderrajput@gmail.com>,
mingo@redhat.com, dwmw2@infradead.org,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH] Make exported headers use strict posix types
Date: Wed, 25 Feb 2009 21:11:31 +0100 [thread overview]
Message-ID: <20090225201131.GA26110@uranus.ravnborg.org> (raw)
In-Reply-To: <200902251917.49017.arnd@arndb.de>
On Wed, Feb 25, 2009 at 07:17:47PM +0100, Arnd Bergmann wrote:
> 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_int32_t, uint32_t, u32,
> uint and the signed and 8/16/64 bit variants thereof), which we may
> want to do in an automated script instead.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
>
> This is my previous patch, ported to today's git. It's my last day
> before my vacation, so I can't do the usual testing etc. on it.
> Hopefully somebody else can take care of this.
I hesitate to put it in kbuild.git... Any better place?
> diff --git a/include/linux/coda_psdev.h b/include/linux/coda_psdev.h
> index 07ae8f8..ebdc055 100644
> --- a/include/linux/coda_psdev.h
> +++ b/include/linux/coda_psdev.h
> @@ -6,6 +6,7 @@
> #define CODA_PSDEV_MAJOR 67
> #define MAX_CODADEVS 5 /* how many do we allow */
>
> +#ifdef __KERNEL__
> struct kstatfs;
>
> /* communication pending/processing queues */
> @@ -89,4 +90,5 @@ struct upc_req {
>
> extern struct venus_comm coda_comms[];
>
> +#endif /* __KERNEL__ */
> #endif
Does this change really belong in this patchset?
> diff --git a/include/linux/compiler-gcc4.h b/include/linux/compiler-gcc4.h
> index 0999271..f6dcc29 100644
> --- a/include/linux/compiler-gcc4.h
> +++ b/include/linux/compiler-gcc4.h
> @@ -4,7 +4,7 @@
>
> /* GCC 4.1.[01] miscompiles __weak */
> #if __GNUC_MINOR__ == 1 && __GNUC_PATCHLEVEL__ <= 1
> -# error Your version of gcc miscompiles the __weak directive
> +// # error Your version of gcc miscompiles the __weak directive
> #endif
>
> #define __used __attribute__((__used__))
Yes - I can build kernels again. But I think we should skip this change..
> diff --git a/include/linux/mroute6.h b/include/linux/mroute6.h
> index 5375fac..43dc97e 100644
> --- a/include/linux/mroute6.h
> +++ b/include/linux/mroute6.h
> @@ -65,7 +65,7 @@ struct mif6ctl {
> mifi_t mif6c_mifi; /* Index of MIF */
> unsigned char mif6c_flags; /* MIFF_ flags */
> unsigned char vifc_threshold; /* ttl limit */
> - u_short mif6c_pifi; /* the index of the physical IF */
> + __u16 mif6c_pifi; /* the index of the physical IF */
> unsigned int vifc_rate_limit; /* Rate limiter values (NI) */
> };
>
This change looks correct - but I assume this is a separate patch.
Rest looks good.
Sam
next prev parent reply other threads:[~2009-02-25 20:09 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 [this message]
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
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=20090225201131.GA26110@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=arnd@arndb.de \
--cc=dwmw2@infradead.org \
--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 \
/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