linux-kernel - Re: [Patch v3] driver/i2c/mux: Add register-based mux i2c-mux-reg

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:	Tue, 11 Aug 2015 22:02:54 +0200
From:	Wolfram Sang <wsa@...-dreams.de>
To:	York Sun <yorksun@...escale.com>
Cc:	linux-kernel@...r.kernel.org, linux-i2c@...r.kernel.org,
	Paul Bolle <pebolle@...cali.nl>,
	Peter Korsgaard <peter.korsgaard@...co.com>,
	Alexander Sverdlin <alexander.sverdlin@...ia.com>
Subject: Re: [Patch v3] driver/i2c/mux: Add register-based mux i2c-mux-reg

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


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