linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@openedhand.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: dbrownell@users.sourceforge.net,
	OMAP <linux-omap@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Mark Brown <broonie@sirena.org.uk>
Subject: Re: [patch] twl4030-regulator: expose VPLL2
Date: Sun, 22 Mar 2009 20:19:35 +0100	[thread overview]
Message-ID: <20090322191935.GB2832@sortiz.org> (raw)
In-Reply-To: <1237486426.6781.345.camel@vega.slimlogic.co.uk>

On Thu, Mar 19, 2009 at 06:13:46PM +0000, Liam Girdwood wrote:
> On Mon, 2009-03-16 at 15:51 +0000, Mark Brown wrote:
> > On Fri, Mar 13, 2009 at 05:54:54PM -0700, David Brownell wrote:
> > > From: David Brownell <dbrownell@users.sourceforge.net>
> > > 
> > > Add VPLL2 to the set of twl4030-family regulators exposed for
> > > use by various drivers.  It's commonly used to power the digital
> > > video outputs (e.g. LCD or DVI displays) on OMAP3 systems.
> > > 
> > > Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
> > 
> > Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> 
> Samuel, I've applied this to the regulator tree as the part that touches
> mfd is relatively minor and twl4030 specific (doesn't touch core).
Thanks a lot, and sorry for the late reply...
Feel free to add my Acked-by: if needed.

Cheers,
Samuel.

 
> Thanks
> 
> Liam
> 

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

  reply	other threads:[~2009-03-22 19:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-14  0:54 [patch] twl4030-regulator: expose VPLL2 David Brownell
2009-03-16 11:43 ` Liam Girdwood
2009-03-16 15:51 ` Mark Brown
2009-03-19 18:13   ` Liam Girdwood
2009-03-22 19:19     ` Samuel Ortiz [this message]
2009-03-20 18:47 ` [APPLIED] " Tony Lindgren

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=20090322191935.GB2832@sortiz.org \
    --to=sameo@openedhand.com \
    --cc=broonie@sirena.org.uk \
    --cc=dbrownell@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --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).