linux-kernel - Re: [PATCH v2 3/7] usb: phy: msm: Move regulator usage to managed resource allocation

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]

Message-ID: <1374908081.29094.1.camel@localhost>
Date:	Sat, 27 Jul 2013 09:54:41 +0300
From:	"Ivan T. Ivanov" <iivanov@...sol.com>
To:	balbi@...com
Cc:	gregkh@...uxfoundation.org, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v2 3/7] usb: phy: msm: Move regulator usage to managed
 resource allocation

On Fri, 2013-07-26 at 23:28 +0300, Felipe Balbi wrote:
> On Fri, Jul 26, 2013 at 03:31:34PM +0300, Ivan T. Ivanov wrote:
> > 
> > Hi Felipe, 
> > 
> > On Thu, 2013-07-25 at 16:43 +0300, Ivan T. Ivanov wrote:
> > > On Wed, 2013-07-24 at 15:39 +0300, Felipe Balbi wrote:
> > > > On Tue, Jul 09, 2013 at 06:47:09PM +0300, Ivan T. Ivanov wrote:
> > > > > From: "Ivan T. Ivanov" <iivanov@...sol.com>
> > > > > 
> > > > > This patch move global regulators variables to driver state
> > > > > structire and move allocation of the regulators to be devm managed.
> > > > 
> > > > split into two patches please. One for moving the global regulators into
> > > > your structure and a separate patch to move to devm_*
> > > > 
> > 
> > Would you accept patch which convert all resources allocation to devm_
> > variants in single patch or you prefer separate patches for memory, 
> > clocks, regulators and irq?
> 
> devm_* all over the place should be fine ;-)
> 

Thanks, it is coming. 

Regards,
Ivan

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