From: Arjan van de Ven <arjan@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Harvey Harrison <harvey.harrison@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
bluebird@gentoo.org, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: [PATCH-2.6.28 final] byteorder: fix new headers for userspace
Date: Fri, 19 Dec 2008 09:08:56 +0100 [thread overview]
Message-ID: <20081219090856.48666b14@infradead.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0812181246420.14014@localhost.localdomain>
On Thu, 18 Dec 2008 12:47:28 -0800 (PST)
Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
>
> On Thu, 18 Dec 2008, Linus Torvalds wrote:
> >
> > I think it would be better to just make it a config option, call it
> > CONFIG_[LITTLE|BIG]_ENDIAN and set it up in the architecture
> > Kconfig file. I think some of the people who can set it dynamically
> > (or where it depends on the target machine) already effectively do
> > that.
>
> Never mind, since we end up having to export it to user space (do
> we?) we can't depend on the config.h file, nor can we pollute the
> name space.
>
why are we exposing byte order functions to userspace in the first
place ????
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-12-19 8:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4943DAD6.7070402@gentoo.org>
2008-12-16 9:13 ` Compiling glibc with 2.6.28 linux headers David Miller
2008-12-17 1:22 ` Harvey Harrison
2008-12-18 1:46 ` [PATCH-2.6.28 final] byteorder: fix new headers for userspace Harvey Harrison
2008-12-18 20:09 ` Linus Torvalds
2008-12-18 20:47 ` Linus Torvalds
2008-12-18 20:53 ` Harvey Harrison
2008-12-19 8:08 ` Arjan van de Ven [this message]
2008-12-19 16:37 ` Harvey Harrison
2009-01-06 10:23 ` Gerd Hoffmann
2009-01-06 16:41 ` Harvey Harrison
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=20081219090856.48666b14@infradead.org \
--to=arjan@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bluebird@gentoo.org \
--cc=davem@davemloft.net \
--cc=harvey.harrison@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=torvalds@linux-foundation.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®