From: Keerthy <a0393675@ti.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: J Keerthy <j-keerthy@ti.com>,
linux-omap@vger.kernel.org, grant.likely@secretlab.ca,
broonie@kernel.org, ldewangan@nvidia.com, sameo@linux.intel.com,
swarren@nvidia.com, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
gg@slimlogic.co.uk
Subject: Re: [PATCH 1/4] MFD: Add TPS659038 documentation under Palmas
Date: Thu, 11 Jul 2013 16:14:17 +0530 [thread overview]
Message-ID: <51DE8C81.9090009@ti.com> (raw)
In-Reply-To: <20130711104327.GE25601@gmail.com>
On Thursday 11 July 2013 04:13 PM, Lee Jones wrote:
> On Thu, 20 Jun 2013, J Keerthy wrote:
>
>> Add TPS659038 documentation under Palmas.
>>
>> Signed-off-by: J Keerthy <j-keerthy@ti.com>
>> Acked-by: Samuel Ortiz <sameo@linux.intel.com>
>> ---
>> Documentation/devicetree/bindings/mfd/palmas.txt | 2 ++
>> 1 files changed, 2 insertions(+), 0 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/mfd/palmas.txt b/Documentation/devicetree/bindings/mfd/palmas.txt
>> index 7bcd59c..89cb773 100644
>> --- a/Documentation/devicetree/bindings/mfd/palmas.txt
>> +++ b/Documentation/devicetree/bindings/mfd/palmas.txt
>> @@ -5,6 +5,7 @@ twl6035 (palmas)
>> twl6037 (palmas)
>> tps65913 (palmas)
>> tps65914 (palmas)
>> +tps659038
>>
>> Required properties:
>> - compatible : Should be from the list
>> @@ -14,6 +15,7 @@ Required properties:
>> ti,tps65913
>> ti,tps65914
>> ti,tps80036
>> + ti,tps659038
>> and also the generic series names
>> ti,palmas
>> - interrupt-controller : palmas has its own internal IRQs
> Applied.
Thanks Lee Jones.
>
prev parent reply other threads:[~2013-07-11 10:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 11:04 [PATCH 1/4] MFD: Add TPS659038 documentation under Palmas J Keerthy
2013-06-24 12:55 ` J, KEERTHY
2013-06-27 4:32 ` J, KEERTHY
2013-07-02 9:42 ` J, KEERTHY
2013-07-11 9:34 ` Lee Jones
2013-07-11 10:43 ` Lee Jones
2013-07-11 10:44 ` Keerthy [this message]
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=51DE8C81.9090009@ti.com \
--to=a0393675@ti.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=lee.jones@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sameo@linux.intel.com \
--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).