linux-kernel - Re: [PATCH] mfd: da9052-core: Fix platform-device id collision

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]

Message-ID: <20141210121125.GC23481@x1>
Date:	Wed, 10 Dec 2014 12:11:25 +0000
From:	Lee Jones <lee.jones@...aro.org>
To:	Mark Brown <broonie@...nel.org>
Cc:	Fabio Estevam <festevam@...il.com>, sameo@...ux.intel.com,
	anthony.olech.opensource@...semi.com,
	support.opensource@...semi.com, johan@...nel.org,
	linux-kernel@...r.kernel.org,
	Fabio Estevam <fabio.estevam@...escale.com>
Subject: Re: [PATCH] mfd: da9052-core: Fix platform-device id collision

On Wed, 10 Dec 2014, Mark Brown wrote:

> On Wed, Dec 10, 2014 at 09:46:50AM +0000, Lee Jones wrote:
> > On Tue, 09 Dec 2014, Fabio Estevam wrote:
> 
> > > Tested on a imx53-qsb board, where multiple DA9053 regulators can be 
> > > successfully probed.
> 
> > Applied for v3.20, thanks.
> 
> Fabio was saying that -next is broken which presumably means that v3.19
> will be broken unless this gets sent as a fix.

My train of thought was that the original configuration has not
changed since 2011.  I guess other regulators have been recently
introduced.  Very well, applied to -fixes.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/