From: Samuel Ortiz <sameo@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Graeme Gregory <gg@slimlogic.co.uk>,
linux-kernel@vger.kernel.org, lrg@ti.com, b-cousson@ti.com,
linux-omap@vger.kernel.org
Subject: Re: [PATCHv2 1/4] MFD: palmas PMIC device support
Date: Fri, 18 May 2012 11:55:12 +0200 [thread overview]
Message-ID: <20120518095512.GF12015@sortiz-mobl> (raw)
In-Reply-To: <20120515181448.GD19592@opensource.wolfsonmicro.com>
Hi Mark,
On Tue, May 15, 2012 at 07:14:51PM +0100, Mark Brown wrote:
> On Tue, May 15, 2012 at 03:48:56PM +0900, Graeme Gregory wrote:
> > Palmas is a PMIC from Texas Instruments and this is the MFD part of the
> > driver for this chip. The PMIC has SMPS and LDO regulators, a general
> > purpose ADC, GPIO, USB OTG mode detection, watchdog and RTC features.
>
> Reviwed-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
>
> however this depends on some new regmap-irq changes that Graeme posted a
> couple of days ago and are only on regmap at the minute - Samuel, if
> you're OK with this I guess the easiest thing is if I apply there?
I'm fine with it. For the MFD parts:
Acked-by: Samuel Ortiz <sameo@linux.intel.com>
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2012-05-18 9:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 6:48 [PATCHv2 0/4] Adding support for Palmas PMIC Graeme Gregory
2012-05-15 6:48 ` [PATCHv2 1/4] MFD: palmas PMIC device support Graeme Gregory
2012-05-15 18:14 ` Mark Brown
2012-05-18 9:55 ` Samuel Ortiz [this message]
2012-05-18 16:23 ` Mark Brown
2012-05-15 6:48 ` [PATCHv2 2/4] MFD: palmas PMIC device support Kconfig Graeme Gregory
2012-05-15 6:48 ` [PATCHv2 3/4] REGULATOR: regulator driver for Palmas series chips Graeme Gregory
2012-05-15 18:19 ` Mark Brown
2012-05-15 6:48 ` [PATCHv2 4/4] REGULATOR: regulator for Palmas Kconfig Graeme Gregory
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=20120518095512.GF12015@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=b-cousson@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=lrg@ti.com \
/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).