linux-kernel - Re: [PATCHv3] PCAP regulator driver (for 2.6.32)

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: <1246271291.30631.40.camel@vega.slimlogic.co.uk>
Date:	Mon, 29 Jun 2009 11:28:11 +0100
From:	Liam Girdwood <lrg@...mlogic.co.uk>
To:	Daniel Ribeiro <drwyrm@...il.com>
Cc:	Samuel Ortiz <sameo@...ux.intel.com>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	openezx-devel <openezx-devel@...ts.openezx.org>
Subject: Re: [PATCHv3] PCAP regulator driver (for 2.6.32)

On Mon, 2009-06-29 at 11:23 +0100, Liam Girdwood wrote:
> On Sat, 2009-06-27 at 14:26 -0300, Daniel Ribeiro wrote:
> > Em Sáb, 2009-06-27 às 11:51 +0100, Mark Brown escreveu:
> > > On Sat, Jun 27, 2009 at 12:18:02AM -0300, Daniel Ribeiro wrote:
> > > > Add (partial) support for the voltage regulators on the PCAP2 PMIC.
> > > > 
> > > > Signed-off-by: Daniel Ribeiro <drwyrm@...il.com>
> > > 
> > > Acked-by: Mark Brown <broonie@...nsource.wolfsonmicro.com>
> > > 
> > > Looks good.
> > 
> > Thanks.
> > 
> > > > Mark, can you please assert that this only gets merged after Samuel has
> > > > a chance to merge the set_bits patch? Thanks!
> > > 
> > > It's Liam who manages the regulator tree, though given the set_bits()
> > > patch perhaps this one might end up getting merged via the MFD tree (or
> > > both via the regulator tree).
> > 
> > I prefer the set_bits() patch going through the MFD tree. I sent some
> > other fixes, and a patch to solve a similar race issue for the ADC/TS
> > driver.
> > 
> 
> Is this a runtime or build time dependency for this patch ? I'm thinking
> about not breaking -next builds.  

Ah, just seen your earlier patch. Looks like we need this to build. 

Liam

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