linux-kernel - Re: [PATCH] regulator: core: Correct default return value for full constraints

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] [day] [month] [year] [list]

Date:	Mon, 3 Feb 2014 17:31:04 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Guenter Roeck <linux@...ck-us.net>
Cc:	Jean Delvare <khali@...ux-fr.org>,
	Liam Girdwood <lgirdwood@...il.com>,
	linux-kernel@...r.kernel.org, linaro-kernel@...ts.linaro.org
Subject: Re: [PATCH] regulator: core: Correct default return value for full
 constraints

On Mon, Feb 03, 2014 at 08:52:10AM -0800, Guenter Roeck wrote:
> On Mon, Feb 03, 2014 at 03:41:09PM +0000, Mark Brown wrote:

> > It's on a fixes tag so it'll go in next time I send stuff to Linus,
> > it'll go next time I send something to him.  That's usually about once
> > per release.  Especially if things are tagged for stable I like to try
> > to avoid sending them too quickly unless they're build breaks or
> > similar.

> We still have the lm90 driver failing in 13.3 for non-DT platforms.
> One should think that this has some level of importance. If a driver
> doesn't build or doesn't work makes little difference for the user,
> after all.

On the other hand it's a hardware monitoring driver which nobody managed
to notice problems with for pretty much an entire release cycle and a
fix in the core regulator lookup code which has the ability to break
boot prior to the console coming up if it goes wrong.  An extra week is
not going to be the end of the world here but helps ensure better
exposure of what hits stable.

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