From: Mark Brown <broonie@kernel.org>
To: Keerthy <j-keerthy@ti.com>
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: Tue, 28 May 2019 14:27:55 +0100 [thread overview]
Message-ID: <20190528132755.GK2456@sirena.org.uk> (raw)
In-Reply-To: <1712197d-7d43-38a8-efde-11b99537eae9@ti.com>
[-- Attachment #1: Type: text/plain, Size: 405 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-05-28 13:28 UTC|newest]
Thread overview: 20+ 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 ` Keerthy
2019-05-16 4:32 ` [PATCH v2 1/3] dt-bindings: mfd: lp87565: Add lp87561 configuration Keerthy
2019-05-16 4:32 ` 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 ` Keerthy
2019-05-16 4:32 ` [PATCH v2 3/3] regulator: lp87565: Add 4-phase lp87561 regulator support Keerthy
2019-05-16 4:32 ` Keerthy
2019-05-22 15:35 ` Mark Brown
2019-05-28 9:53 ` Keerthy
2019-05-28 9:53 ` Keerthy
2019-05-28 13:27 ` Mark Brown [this message]
2019-06-08 3:56 ` keerthy
2019-06-08 3:56 ` keerthy
2019-06-08 19:51 ` Mark Brown
2019-06-10 5:48 ` Lee Jones
2019-06-12 10:47 ` Keerthy
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=20190528132755.GK2456@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j-keerthy@ti.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.