From: Mark Brown <broonie@kernel.org>
To: Colin Ian King <colin.king@canonical.com>
Cc: Lee Jones <lee.jones@linaro.org>, Keerthy <j-keerthy@ti.com>,
Liam Girdwood <lgirdwood@gmail.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] regulator: lp87565: fix missing break in switch statement
Date: Tue, 2 Jul 2019 13:24:26 +0100 [thread overview]
Message-ID: <20190702122426.GI2793@sirena.org.uk> (raw)
In-Reply-To: <4a0a50be-1465-0554-f787-dec72bc07a00@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 684 bytes --]
On Tue, Jul 02, 2019 at 12:12:10PM +0100, Colin Ian King wrote:
> On 02/07/2019 11:44, Lee Jones wrote:
> > On Fri, 28 Jun 2019, Colin Ian King wrote:
> >> So it applies cleanly against linux-next, I think the original code
> >> landed in mfd/for-mfd-next - c.f. https://lkml.org/lkml/2019/5/28/550
> > Applied, thanks Colin.
> I'm confused, who is the official maintainer of the regulator patches
> nowadays?
Me and Liam but since this patch only applies against Lee's tree he's
applied it there (I didn't think it was worth me picking up the entire
cross tree merge branch Lee prepared for this one fix, if Lee hadn't
picked it up it'd have waited till after the merge window).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-07-02 12:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 13:16 [PATCH][next] regulator: lp87565: fix missing break in switch statement Colin King
2019-06-28 3:28 ` Keerthy
2019-06-28 14:36 ` Mark Brown
2019-06-28 21:18 ` Colin Ian King
2019-07-02 10:44 ` Lee Jones
2019-07-02 11:12 ` Colin Ian King
2019-07-02 11:31 ` Lee Jones
2019-07-02 11:36 ` Keerthy
2019-07-02 12:24 ` Mark Brown [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=20190702122426.GI2793@sirena.org.uk \
--to=broonie@kernel.org \
--cc=colin.king@canonical.com \
--cc=j-keerthy@ti.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.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