From: Keerthy <a0393675@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: Keerthy <j-keerthy@ti.com>,
rob.herring@calxeda.com, pawel.moll@arm.com,
mark.rutland@arm.com, swarren@wwwdotorg.org,
ijc+devicetree@hellion.org.uk, rob@landley.net,
sameo@linux.intel.com, lee.jones@linaro.org,
grant.likely@linaro.org, lgirdwood@gmail.com,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH v2 3/4] Regulators: TPS65218: Add Regulator driver for TPS65218 PMIC
Date: Tue, 18 Feb 2014 13:52:00 +0530 [thread overview]
Message-ID: <53031828.20000@ti.com> (raw)
In-Reply-To: <20140214202108.GI4451@sirena.org.uk>
On Saturday 15 February 2014 01:51 AM, Mark Brown wrote:
> On Thu, Feb 06, 2014 at 11:20:13AM +0530, Keerthy wrote:
>> This patch adds support for TPS65218 PMIC regulators.
>>
>> The regulators set consists of 6 DCDCs and 1 LDO. The output
>> voltages are configurable and are meant to supply power to the
>> main processor and other components.
> Applied, thanks. Please use subject lines consistent with the
> subsystem.
Sure. Thanks a lot Mark.
next prev parent reply other threads:[~2014-02-18 8:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 5:50 [PATCH 0/4] [PATCH v2 0/4] MFD: TPS65218: Drivers for TPS65218 PMIC Keerthy
2014-02-06 5:50 ` [PATCH v2 1/4] mfd: DT bindings " Keerthy
2014-02-06 5:50 ` [PATCH v2 2/4] MFD: TPS65218: Add driver for the " Keerthy
2014-02-06 14:37 ` Lee Jones
2014-02-06 17:09 ` Keerthy
2014-02-07 11:12 ` Lee Jones
2014-02-07 13:41 ` Keerthy
2014-02-06 5:50 ` [PATCH v2 3/4] Regulators: TPS65218: Add Regulator driver for " Keerthy
2014-02-07 13:58 ` Keerthy
[not found] ` <52F4E685.4060605-l0cyMroinI0@public.gmane.org>
2014-02-07 17:27 ` Mark Brown
2014-02-14 20:21 ` Mark Brown
2014-02-18 8:22 ` Keerthy [this message]
2014-02-06 5:50 ` [PATCH 4/4] ARM: dts: AM43x: Add dts nodes of " 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=53031828.20000@ti.com \
--to=a0393675@ti.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=j-keerthy@ti.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=sameo@linux.intel.com \
--cc=swarren@wwwdotorg.org \
/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).