From: Felipe Balbi <balbi@ti.com>
To: "Ivan T. Ivanov" <iivanov@mm-sol.com>
Cc: balbi@ti.com, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2 3/7] usb: phy: msm: Move regulator usage to managed resource allocation
Date: Fri, 26 Jul 2013 23:28:20 +0300 [thread overview]
Message-ID: <20130726202820.GA14077@radagast> (raw)
In-Reply-To: <1374841894.1956.42.camel@iivanov-dev.int.mm-sol.com>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
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@mm-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 ;-)
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-26 20:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 15:47 [PATCH v2 0/7] usb: phy: msm: Fixes and cleanups Ivan T. Ivanov
2013-07-09 15:47 ` [PATCH v2 1/7] usb: phy: msm: Move mach depndend code to platform data Ivan T. Ivanov
2013-07-24 12:34 ` Felipe Balbi
2013-07-24 12:36 ` Felipe Balbi
2013-07-09 15:47 ` [PATCH v2 3/7] usb: phy: msm: Move regulator usage to managed resource allocation Ivan T. Ivanov
2013-07-24 12:39 ` Felipe Balbi
2013-07-25 13:43 ` Ivan T. Ivanov
2013-07-26 12:31 ` Ivan T. Ivanov
2013-07-26 20:28 ` Felipe Balbi [this message]
2013-07-27 6:54 ` Ivan T. Ivanov
2013-07-09 15:47 ` [PATCH v2 4/7] usb: phy: msm: Remove unnecessarily check for valid regulators Ivan T. Ivanov
2013-07-09 15:47 ` [PATCH v2 5/7] usb: phy: msm: Fix WARNING: quoted string split across lines Ivan T. Ivanov
2013-07-09 15:47 ` [PATCH v2 7/7] usb: phy: msm: Lindent the code Ivan T. Ivanov
[not found] ` <1373384833-18077-1-git-send-email-iivanov-NEYub+7Iv8PQT0dZR+AlfA@public.gmane.org>
2013-07-09 15:47 ` [PATCH v2 2/7] usb: phy: msm: Migrate to Managed Device Resource allocation Ivan T. Ivanov
[not found] ` <1373384833-18077-3-git-send-email-iivanov-NEYub+7Iv8PQT0dZR+AlfA@public.gmane.org>
2013-07-24 12:38 ` Felipe Balbi
2013-07-25 13:42 ` Ivan T. Ivanov
2013-07-09 15:47 ` [PATCH v2 6/7] usb: phy: msm: Fix WARNING: Prefer seq_puts to seq_printf Ivan T. Ivanov
2013-07-16 11:25 ` [PATCH v2 0/7] usb: phy: msm: Fixes and cleanups Ivan T. Ivanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130726202820.GA14077@radagast \
--to=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=iivanov@mm-sol.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).