From: keerthy <j-keerthy@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: lee.jones@linaro.org, robh+dt@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-omap@vger.kernel.org, t-kristo@ti.com
Subject: Re: [PATCH v2 3/3] regulator: lp87565: Add 4-phase lp87561 regulator support
Date: Sat, 8 Jun 2019 09:26:31 +0530 [thread overview]
Message-ID: <e68d9939-a56a-b3c5-7f6d-e5783e16a6de@ti.com> (raw)
In-Reply-To: <20190528132755.GK2456@sirena.org.uk>
On 5/28/2019 6:57 PM, Mark Brown wrote:
> On Tue, May 28, 2019 at 03:23:41PM +0530, Keerthy wrote:
>> On 22/05/19 9:05 PM, Mark Brown wrote:
>>> On Thu, May 16, 2019 at 10:02:18AM +0530, Keerthy wrote:
>
>>> Acked-by: Mark Brown <broonie@kernel.org>
>
>> This patch will come via the mfd branch?
>
> I'd expect so, IIRC it had a build dependency on the earlier patches in
> the series so if that doesn't happen I'll need to merge the relevant MFD
> commits.
Mark,
mfd patches are on linux-next already. Hope you can pull this one now
that dependencies are met.
- Keerthy
>
next prev parent reply other threads:[~2019-06-08 3:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 4:32 [PATCH v2 0/3] mfd: lp87565: Add support for 4-phase lp87561 combination Keerthy
2019-05-16 4:32 ` [PATCH v2 1/3] dt-bindings: mfd: lp87565: Add lp87561 configuration Keerthy
2019-06-13 21:28 ` Rob Herring
2019-05-16 4:32 ` [PATCH v2 2/3] mfd: lp87565: Add support for 4-phase lp87561 combination Keerthy
2019-05-16 4:32 ` [PATCH v2 3/3] regulator: lp87565: Add 4-phase lp87561 regulator support Keerthy
2019-05-22 15:35 ` Mark Brown
2019-05-28 9:53 ` Keerthy
2019-05-28 13:27 ` Mark Brown
2019-06-08 3:56 ` keerthy [this message]
2019-06-08 19:51 ` Mark Brown
2019-06-10 5:48 ` Lee Jones
2019-06-12 10:47 ` Keerthy
2019-06-12 14:33 ` Lee Jones
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=e68d9939-a56a-b3c5-7f6d-e5783e16a6de@ti.com \
--to=j-keerthy@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=robh+dt@kernel.org \
--cc=t-kristo@ti.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).