All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: 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: Thu, 18 Dec 2008 12:09:54 -0800 (PST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0812181208070.14014@localhost.localdomain> (raw)
In-Reply-To: <1229564779.6481.26.camel@brick>



On Wed, 17 Dec 2008, Harvey Harrison wrote:
>
> glibc headers define both __LITTLE_ENDIAN and __BIG_ENDIAN
> which was tripping the check in linux/byteorder.h.  Let's
> just stay out of userspace's way and use __KERN_{endian}

Gaah, ugly.

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.

Hmm?

		Linus

WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: 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: Thu, 18 Dec 2008 20:09:54 +0000	[thread overview]
Message-ID: <alpine.LFD.2.00.0812181208070.14014@localhost.localdomain> (raw)
In-Reply-To: <1229564779.6481.26.camel@brick>



On Wed, 17 Dec 2008, Harvey Harrison wrote:
>
> glibc headers define both __LITTLE_ENDIAN and __BIG_ENDIAN
> which was tripping the check in linux/byteorder.h.  Let's
> just stay out of userspace's way and use __KERN_{endian}

Gaah, ugly.

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.

Hmm?

		Linus

  reply	other threads:[~2008-12-18 20:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-13 15:55 Compiling glibc with 2.6.28 linux headers Friedrich Oslage
2008-12-16  9:13 ` David Miller
2008-12-16  9:13   ` David Miller
2008-12-17  1:22   ` Harvey Harrison
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  1:46     ` Harvey Harrison
2008-12-18 20:09     ` Linus Torvalds [this message]
2008-12-18 20:09       ` Linus Torvalds
2008-12-18 20:47       ` Linus Torvalds
2008-12-18 20:47         ` Linus Torvalds
2008-12-18 20:53         ` Harvey Harrison
2008-12-18 20:53           ` Harvey Harrison
2008-12-19  8:08         ` Arjan van de Ven
2008-12-19  8:08           ` Arjan van de Ven
2008-12-19 16:37           ` Harvey Harrison
2008-12-19 16:37             ` Harvey Harrison
2009-01-06 10:23     ` Gerd Hoffmann
2009-01-06 10:23       ` Gerd Hoffmann
2009-01-06 16:41       ` Harvey Harrison
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=alpine.LFD.2.00.0812181208070.14014@localhost.localdomain \
    --to=torvalds@linux-foundation.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 \
    /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.