From: Samuel Ortiz <sameo@linux.intel.com>
To: "J, KEERTHY" <j-keerthy@ti.com>
Cc: "broonie@kernel.org" <broonie@kernel.org>,
"ldewangan@nvidia.com" <ldewangan@nvidia.com>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"swarren@nvidia.com" <swarren@nvidia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"gg@slimlogic.co.uk" <gg@slimlogic.co.uk>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v3 2/4] MFD: Palmas: Add SMPS10_BOOST feature
Date: Thu, 20 Jun 2013 11:07:37 +0200 [thread overview]
Message-ID: <20130620090737.GF15667@zurbaran> (raw)
In-Reply-To: <DC88CAD03C0052499C1907B327FC63229ECC05@DBDE04.ent.ti.com>
Hi,
On Thu, Jun 20, 2013 at 04:34:42AM +0000, J, KEERTHY wrote:
> > -----Original Message-----
> > From: J, KEERTHY
> > Sent: Wednesday, June 19, 2013 11:28 AM
> > To: linux-omap@vger.kernel.org
> > Cc: broonie@kernel.org; J, KEERTHY; ldewangan@nvidia.com;
> > sameo@linux.intel.com; grant.likely@secretlab.ca; swarren@nvidia.com;
> > linux-kernel@vger.kernel.org; linux-doc@vger.kernel.org; devicetree-
> > discuss@lists.ozlabs.org; gg@slimlogic.co.uk
> > Subject: [PATCH v3 2/4] MFD: Palmas: Add SMPS10_BOOST feature
> >
> > From: J Keerthy <j-keerthy@ti.com>
> >
> > The SMPS10 regulator is not presesnt in all the variants of the PALMAS
> > PMIC family. Hence adding a feature to distingush between them.
> >
>
> Could you please pull this patch?
I'm reverting this one for now as of_match_device is not define for
!CONFIG_OF.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2013-06-20 9:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 5:57 [PATCH v3 0/4] MFD: Palmas: Add TPS659038 PMIC support on Palmas Keerthy
2013-06-19 5:57 ` [PATCH v3 1/4] MFD: Palmas: Check if irq is valid Keerthy
[not found] ` <1371621470-22279-2-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2013-06-19 16:42 ` Mark Brown
2013-06-20 4:16 ` J, KEERTHY
2013-06-19 17:08 ` Stephen Warren
2013-06-20 4:19 ` J, KEERTHY
2013-06-20 4:25 ` J, KEERTHY
2013-07-11 11:25 ` Lee Jones
2013-07-11 11:27 ` Lee Jones
2013-06-19 5:57 ` [PATCH v3 2/4] MFD: Palmas: Add SMPS10_BOOST feature Keerthy
2013-06-20 4:34 ` J, KEERTHY
2013-06-20 9:07 ` Samuel Ortiz [this message]
2013-06-20 9:13 ` J, KEERTHY
[not found] ` <DC88CAD03C0052499C1907B327FC63229ECDCE-yXqyApvAXouIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2013-06-20 9:27 ` Samuel Ortiz
2013-06-20 9:28 ` J, KEERTHY
2013-06-19 5:57 ` [PATCH v3 3/4] mfd: Palmas: Add TPS659038 PMIC support Keerthy
2013-06-20 8:41 ` Samuel Ortiz
2013-06-19 5:57 ` [PATCH v3 4/4] regulator: Palmas: Add TPS659038 support Keerthy
[not found] ` <1371621470-22279-5-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2013-06-19 16:42 ` Mark Brown
2013-06-20 4:19 ` J, KEERTHY
2013-06-20 8:39 ` [PATCH v3 0/4] MFD: Palmas: Add TPS659038 PMIC support on Palmas Samuel Ortiz
2013-06-20 8:41 ` J, KEERTHY
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=20130620090737.GF15667@zurbaran \
--to=sameo@linux.intel.com \
--cc=broonie@kernel.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=gg@slimlogic.co.uk \
--cc=grant.likely@secretlab.ca \
--cc=j-keerthy@ti.com \
--cc=ldewangan@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=swarren@nvidia.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).