linux-kernel - Re: [PATCH] Revert "regmap-mmio: Use native endianness for read/write"

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20160126113133.GB6588@sirena.org.uk>
Date:	Tue, 26 Jan 2016 11:31:33 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Johannes Berg <johannes@...solutions.net>,
	Simon Arlott <simon@...e.lp0.eu>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Revert "regmap-mmio: Use native endianness for
 read/write"

On Tue, Jan 26, 2016 at 12:01:25AM +0100, Arnd Bergmann wrote:
> On Monday 25 January 2016 22:47:10 Mark Brown wrote:

> > I can't identify *anything* which says we shouldn't use the __raw
> > accessors in architecture neutral code with the possible exception of
> > the __.  Seriously, how is anyone supposed to use this stuff if we have
> > hidden assumptions like this?

> I thought everyone knew by now.

There's always the danger that we might get some new developers!

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)