From: Mark Brown <broonie@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Kevin Cernekee <cernekee@gmail.com>,
linux-kernel@vger.kernel.org, linux-mips@linux-mips.org,
Johannes Berg <johannes@sipsolutions.net>,
Simon Arlott <simon@fire.lp0.eu>
Subject: Re: [PATCH 1/2] regmap: Add explict native endian flag to DT bindings
Date: Wed, 27 Jan 2016 12:19:26 +0000 [thread overview]
Message-ID: <20160127121926.GJ6042@sirena.org.uk> (raw)
In-Reply-To: <1568100.dTeADjCOTa@wuerfel>
[-- Attachment #1: Type: text/plain, Size: 395 bytes --]
On Wed, Jan 27, 2016 at 12:02:19PM +0100, Arnd Bergmann wrote:
> I think the rest of the file also needs to be changed, and we need some
> more explanation about native-endian, which people might think is the
> right one for them when it rarely is in reality (Broadcom MIPS being
> one notable exception).
I'm not sure it's *that* confusing at this point but this is definitely
a lot clearer.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-01-27 12:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 22:46 Mark Brown
2016-01-26 22:46 ` [PATCH RFC 2/2] MIPS: dt: Explicitly specify native endian behaviour for syscon Mark Brown
2016-01-26 23:16 ` Florian Fainelli
2016-01-27 9:37 ` Ralf Baechle
2016-01-27 10:33 ` Jonas Gorski
2016-01-27 10:45 ` Johannes Berg
2016-01-27 11:10 ` Mark Brown
2016-01-27 18:51 ` Mark Brown
2016-01-27 11:02 ` [PATCH 1/2] regmap: Add explict native endian flag to DT bindings Arnd Bergmann
2016-01-27 12:19 ` Mark Brown [this message]
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=20160127121926.GJ6042@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=cernekee@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=simon@fire.lp0.eu \
/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®