From: Lee Jones <lee.jones@linaro.org>
To: J Keerthy <j-keerthy@ti.com>
Cc: linux-kernel@vger.kernel.org, grant.likely@secretlab.ca,
linux-doc@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
swarren@wwwdotorg.org, swarren@nvidia.com,
rob.herring@calxeda.com, rob@landley.net, sameo@linux.intel.com,
wim@iguana.be, lgirdwood@gmail.com, gg@slimlogic.co.uk,
t-kristo@ti.com, Ian Lartey <ian@slimlogic.co.uk>
Subject: Re: [PATCH v3] mfd: DT bindings for the palmas family MFD
Date: Thu, 6 Jun 2013 08:02:10 +0100 [thread overview]
Message-ID: <20130606070210.GR3370@gmail.com> (raw)
In-Reply-To: <1370496441-24620-1-git-send-email-j-keerthy@ti.com>
On Thu, 06 Jun 2013, J Keerthy wrote:
> Add the various binding files for the palmas family of chips. There is a
> top level MFD binding then a seperate binding for regulators IP blocks on chips.
>
> Signed-off-by: Graeme Gregory <gg@slimlogic.co.uk>
> Signed-off-by: J Keerthy <j-keerthy@ti.com>
> Signed-off-by: Ian Lartey <ian@slimlogic.co.uk>
> Reviewed-by: Stephen Warren <swarren@nvidia.com>
> ---
> Documentation/devicetree/bindings/mfd/palmas.txt | 49 +++++++++++++
> .../devicetree/bindings/regulator/palmas-pmic.txt | 72 ++++++++++++++++++++
> 2 files changed, 121 insertions(+), 0 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/mfd/palmas.txt
> create mode 100644
> Documentation/devicetree/bindings/regulator/palmas-pmic.tx
Applied, thanks.
--
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2013-06-06 7:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 5:27 [PATCH v3] mfd: DT bindings for the palmas family MFD J Keerthy
2013-06-06 7:02 ` Lee Jones [this message]
2013-06-06 7:06 ` Lee Jones
2013-06-07 2:02 ` J, KEERTHY
2013-06-10 9:27 ` J, KEERTHY
2013-06-10 9:55 ` Lee Jones
2013-06-12 8:24 ` J, KEERTHY
2013-06-12 9:29 ` Grant Likely
2013-06-12 9:44 ` 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=20130606070210.GR3370@gmail.com \
--to=lee.jones@linaro.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=gg@slimlogic.co.uk \
--cc=grant.likely@secretlab.ca \
--cc=ian@slimlogic.co.uk \
--cc=j-keerthy@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=sameo@linux.intel.com \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
--cc=t-kristo@ti.com \
--cc=wim@iguana.be \
/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).