From: Arnd Bergmann <arnd@arndb.de>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Andreas Schwab <schwab@suse.de>,
linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
David Woodhouse <dwmw2@infradead.org>,
Jan Engelhardt <jengelh@computergmbh.de>,
Patrick McHardy <kaber@trash.net>,
"David S. Miller" <davem@davemloft.net>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] linux/types.h: always export 64bit aligned defines
Date: Fri, 2 Jan 2009 23:53:06 +0100 [thread overview]
Message-ID: <200901022353.07200.arnd@arndb.de> (raw)
In-Reply-To: <200901021706.25276.vapier@gentoo.org>
On Friday 02 January 2009, Mike Frysinger wrote:
> On Friday 02 January 2009 16:59:35 Andreas Schwab wrote:
>
> > I mean that it may conflict with normal userspace which is the whole
> > point of being hidden.
>
> no, there is nothing in userspace that i know of that defines this type. i
> mentioned this in the changelog already.
What Andreas is trying to explain to you is that the definition of
__KERNEL_STRICT_NAMES is that you would get no definitions that can
possibly pollute the name space, rather than not adding any known
conflicts (which we try with and without __KERNEL_STRICT_NAMES).
The correct patch would add new definitions for __kernel_aligned_{u,be,le}64
types that can be safely used in public data structures even with
__KERNEL_STRICT_NAMES set, and then add the existing names
for convenience for use inside of the kernel, as we do for all the
common types.
Arnd <><
prev parent reply other threads:[~2009-01-02 22:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 8:39 [PATCH v2] linux/types.h: always export 64bit aligned defines Mike Frysinger
2009-01-02 14:24 ` Andreas Schwab
2009-01-02 20:47 ` Mike Frysinger
2009-01-02 21:59 ` Andreas Schwab
2009-01-02 22:06 ` Mike Frysinger
2009-01-02 22:53 ` Arnd Bergmann [this message]
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=200901022353.07200.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=jengelh@computergmbh.de \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=schwab@suse.de \
--cc=vapier@gentoo.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.