linux-kernel - Re: linux-next: build warning in Linus'tree

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 26 May 2010 08:29:45 +0200
From:	Joakim Tjernlund <joakim.tjernlund@...nsmode.se>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
	Linus <torvalds@...ux-foundation.org>
Subject: Re: linux-next: build warning in Linus'tree

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.

I suspect fixing this entails moving all endian tests to #if __BYTE_ORDER ...
and then always define both __LITTLE_ENDIAN and __BIG_ENDIAN

 Jocke

--
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/