From: Liam Girdwood <lrg@ti.com>
To: "Balbi, Felipe" <balbi@ti.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Graeme Gregory <gg@slimlogic.co.uk>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>,
"linux@slimlogic.co.uk" <linux@slimlogic.co.uk>,
"Krishnamoorthy, Balaji T" <balajitk@ti.com>
Subject: Re: [PATCH v4 2/2] USB: TWL6025 allow different regulator name
Date: Mon, 23 May 2011 13:58:44 +0100 [thread overview]
Message-ID: <4DDA5A04.7050703@ti.com> (raw)
In-Reply-To: <20110523111326.GD5663@legolas.emea.dhcp.ti.com>
On 23/05/11 12:13, Balbi, Felipe wrote:
> Hi,
>
> On Mon, May 23, 2011 at 10:58:27AM +0100, Liam Girdwood wrote:
>> On 22/05/11 23:51, Mark Brown wrote:
>>> On Sun, May 22, 2011 at 09:21:24PM +0100, Graeme Gregory wrote:
>>>> The twl6025 uses a different regulator for USB than the 6030 so select
>>>> the correct regulator name depending on the subclass of device.
>>>
>>> Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
>>
>> Acked-by: Liam Girdwood <lrg@ti.com>
>
> Maybe it's better for you to carry this one Liam. I'm done taking
> patches for this merge window and this is related to the same series
> adding support to twl6025. Either that or this will be pending until
> 2.6.41 merge window.
>
Ok, I've now applied it to regulator.
Thanks !
Liam
prev parent reply other threads:[~2011-05-23 12:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 20:21 [PATCH v4 0/1] Add support for twl6025 PMIC Graeme Gregory
2011-05-22 20:21 ` [PATCH v4 1/2] REGULATOR: TWL6025: add support to twl-regulator Graeme Gregory
2011-05-22 22:48 ` Mark Brown
2011-05-23 9:57 ` Liam Girdwood
2011-05-22 20:21 ` [PATCH v4 2/2] USB: TWL6025 allow different regulator name Graeme Gregory
2011-05-22 22:51 ` Mark Brown
2011-05-23 9:58 ` Liam Girdwood
2011-05-23 11:13 ` Felipe Balbi
2011-05-23 12:58 ` Liam Girdwood [this message]
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=4DDA5A04.7050703@ti.com \
--to=lrg@ti.com \
--cc=balajitk@ti.com \
--cc=balbi@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=gg@slimlogic.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@slimlogic.co.uk \
--cc=lrg@slimlogic.co.uk \
/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).