linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: York Sun <yorksun@freescale.com>
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
	Paul Bolle <pebolle@tiscali.nl>,
	Peter Korsgaard <peter.korsgaard@barco.com>,
	Alexander Sverdlin <alexander.sverdlin@nokia.com>
Subject: Re: [Patch v3] driver/i2c/mux: Add register-based mux i2c-mux-reg
Date: Tue, 11 Aug 2015 22:02:54 +0200	[thread overview]
Message-ID: <20150811200254.GC1523@katana> (raw)
In-Reply-To: <55CA2472.9080000@freescale.com>

[-- Attachment #1: Type: text/plain, Size: 422 bytes --]

> > I'd think that "little-endian" or "big-endian" force a setting. If none
> > is present, we shall take the CPU endianess. Or am I overlooking
> > something?
> 
> You are right. The current code checks for littel-endian property. If missing,
> the CPU endianess is used. Do you prefer to check littlen-endian first, if
> missing then big-endian, if both missing then use CPU endianess?

Yes. Do it like this.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-08-11 20:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18 19:57 [Patch v3] driver/i2c/mux: Add register-based mux i2c-mux-reg York Sun
2015-06-19  6:28 ` Alexander Sverdlin
2015-08-11 15:39 ` Wolfram Sang
2015-08-11 15:55   ` York Sun
2015-08-11 16:16     ` Wolfram Sang
2015-08-11 16:36       ` York Sun
2015-08-11 20:02         ` Wolfram Sang [this message]
2015-08-11 21:04           ` York Sun
2015-08-12  1:35             ` Wolfram Sang
2015-08-13 15:57               ` York Sun
2015-08-14 18:27                 ` Wolfram Sang

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=20150811200254.GC1523@katana \
    --to=wsa@the-dreams.de \
    --cc=alexander.sverdlin@nokia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=peter.korsgaard@barco.com \
    --cc=yorksun@freescale.com \
    /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;
as well as URLs for NNTP newsgroup(s).