| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <20100525234116.71889c71.akpm@linux-foundation.org> Date: Tue, 25 May 2010 23:41:16 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: Joakim Tjernlund <joakim.tjernlund@...nsmode.se> Cc: Stephen Rothwell <sfr@...b.auug.org.au>, linux-kernel@...r.kernel.org, linux-next@...r.kernel.org, Linus <torvalds@...ux-foundation.org> Subject: Re: linux-next: build warning in Linus'tree On Wed, 26 May 2010 08:29:45 +0200 Joakim Tjernlund <joakim.tjernlund@...nsmode.se> wrote: > Stephen Rothwell <sfr@...b.auug.org.au> wrote on 2010/05/26 06:09:00: > > > > Hi Andrew, > > > > On Tue, 25 May 2010 18:20:40 -0700 Andrew Morton <akpm@...ux-foundation.org> wrote: > > > > > > hmpf. Does this fix? > > > > No. > > > > The problem is that __LITTLE_ENDIAN is only defined in > > linux/byteorder/little_endian.h which is only included by little endian > > architectures ... > > Ah, not sure how to fix this ATM. Perhaps best to revert > crc32: use __BYTE_ORDER macro for endian detection > for now. yup. > I suspect fixing this entails moving all endian tests to #if __BYTE_ORDER ... > and then always define both __LITTLE_ENDIAN and __BIG_ENDIAN Yes we can't define __LITTLE_ENDIAN to anything on big-endian without breaking lots of other things. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists