linux-kernel - Re: [PATCH] regulator: core: GPIO #0 is a valid GPIO

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: <20140829190129.GZ29327@sirena.org.uk>
Date:	Fri, 29 Aug 2014 20:01:29 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Dmitry Eremin-Solenikov <dmitry_eremin@...tor.com>
Cc:	linux-kernel@...r.kernel.org, Liam Girdwood <lgirdwood@...il.com>,
	Dirk Behme <dirk.behme@...bosch.com>,
	Gokulkrishnan Nagarajan <Gokulkrishnan.Nagarajan@...bosch.com>
Subject: Re: [PATCH] regulator: core: GPIO #0 is a valid GPIO

On Fri, Aug 29, 2014 at 10:19:16PM +0400, Dmitry Eremin-Solenikov wrote:
> From: Dirk Behme <dirk.behme@...bosch.com>
> 
> With GPIO #0, this if statement will always fail. Remove this, the
> check for gpio_is_valid() is sufficent here.

No, read the archives - this will break boards using zero as default.
Any current boards should be using DT and so shouldn't be using fixed
GPIO numbers in the first place which will mean they'll not end up
getting zero as a valid GPIO.  If you are using zero as a GPIO for some
reason provide a way to specify that the GPIO is a real GPIO and not
just the default value for the struct.

> Change-Id: Ia10e8e9c74e11deba852fcd44040cc275b583cfd
> Signed-off-by: Gokulkrishnan Nagarajan <Gokulkrishnan.Nagarajan@...bosch.com>
> Signed-off-by: Dirk Behme <dirk.behme@...bosch.com>

In any case I can't apply this since you didn't sign it off and please
don't include noise from your internal review system in upstream
postings.

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