From: Liam Girdwood <lrg@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: 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>,
"Balbi, Felipe" <balbi@ti.com>,
"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 1/2] REGULATOR: TWL6025: add support to twl-regulator
Date: Mon, 23 May 2011 10:57:54 +0100 [thread overview]
Message-ID: <4DDA2FA2.2000604@ti.com> (raw)
In-Reply-To: <20110522224857.GA15882@opensource.wolfsonmicro.com>
On 22/05/11 23:48, Mark Brown wrote:
> On Sun, May 22, 2011 at 09:21:23PM +0100, Graeme Gregory wrote:
>> Adding support for the twl6025. Major difference in the twl6025 is the
>> group functionality has been removed from the chip so this affects how
>> regulators are enabled and disabled.
>
> Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
>
>> Since V1
>>
>> Use the features variable passed via platform data instead of calling
>> global function.
>
> Change histories like this should usually come after the --- so things
> like git am strip them out of what actually ends up in git.
Applied.
Thanks
Liam
next prev parent reply other threads:[~2011-05-23 9:57 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 [this message]
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
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=4DDA2FA2.2000604@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).