From: Keerthy <j-keerthy@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: lee.jones@linaro.org, robh+dt@kernel.org, t-kristo@ti.com,
tony@atomide.com, mark.rutland@arm.com,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, afd@ti.com
Subject: Re: [PATCH v2 3/3] regulator: tps65917: Add support for SMPS12
Date: Thu, 25 May 2017 09:05:25 +0530 [thread overview]
Message-ID: <98063d56-b5e7-09dd-2524-0bd83306166e@ti.com> (raw)
In-Reply-To: <20170524172028.baxeku6ei373ckdr@sirena.org.uk>
On Wednesday 24 May 2017 10:50 PM, Mark Brown wrote:
> On Tue, May 23, 2017 at 05:46:56PM +0530, Keerthy wrote:
>> App support for SMPS12 dual phase regulator.
>>
>> Signed-off-by: Keerthy <j-keerthy@ti.com>
>> Acked-by: Lee Jones <lee.jones@linaro.org>
>
> What's the relationship between this and support for the lp87565?
Nothing related. I should have sent this separately. Should i send a v3
separately?
>
next prev parent reply other threads:[~2017-05-25 3:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 12:16 [PATCH v2 0/3] mfd: lp87565: Add lp87565 PMIC support Keerthy
2017-05-23 12:16 ` [PATCH v2 1/3] " Keerthy
2017-05-30 9:23 ` Lee Jones
2017-05-30 9:54 ` Keerthy
[not found] ` <a7204c7c-0cc0-f3a7-56af-d1f0508ad4d1-l0cyMroinI0@public.gmane.org>
2017-05-30 10:12 ` Lee Jones
2017-05-30 10:17 ` Keerthy
2017-05-23 12:16 ` [PATCH v2 2/3] regulator: lp87565: Add support for lp87565 PMIC regulators Keerthy
[not found] ` <1495541816-14801-3-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2017-05-24 17:42 ` Applied "regulator: lp87565: Add support for lp87565 PMIC regulators" to the regulator tree Mark Brown
2017-05-23 12:16 ` [PATCH v2 3/3] regulator: tps65917: Add support for SMPS12 Keerthy
2017-05-24 17:20 ` Mark Brown
2017-05-25 3:35 ` Keerthy [this message]
[not found] ` <98063d56-b5e7-09dd-2524-0bd83306166e-l0cyMroinI0@public.gmane.org>
2017-05-25 16:24 ` Mark Brown
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=98063d56-b5e7-09dd-2524-0bd83306166e@ti.com \
--to=j-keerthy@ti.com \
--cc=afd@ti.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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