From: Mark Brown <broonie@kernel.org>
To: Dan Murphy <dmurphy@ti.com>
Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
lee.jones@linaro.org, lgirdwood@gmail.com
Subject: Re: [GIT PULL] Immutable branch between LEDs, MFD and REGULATOR
Date: Wed, 22 May 2019 11:59:58 +0100 [thread overview]
Message-ID: <20190522105958.GA8582@sirena.org.uk> (raw)
In-Reply-To: <151079e6-4ae3-3b95-2dc1-c57927b0425f@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
On Tue, May 21, 2019 at 07:48:18PM -0500, Dan Murphy wrote:
> On 5/21/19 4:15 PM, Mark Brown wrote:
> > On Tue, May 21, 2019 at 10:30:38PM +0200, Jacek Anaszewski wrote:
> >> regulator: lm363x: Make the gpio register enable flexible
> >> regulator: lm363x: Add support for LM36274
> > Why have these been applied, I haven't reviewed them? As far as I can
> > tell they were sent before the merge window so I'd expect a resend at
> > this point...
> You and Liam were cc'd on April 10,2019 for v2 of this patch set. So I am not sure why the review was missed.
> My apologies for not cc'ing you on v4 but there were no change since that time.
Perhaps I was busy, perhaps I saw that the series had other problems and
needed a rework as it was so I just waited for the resend in case they
had knock on effects on the regulator patches.
> I cannot find v3 of this patchset.
> The initial patches were sent on April 5, 2019
And not CCed to maintainers... AFAICT I got at most one copy of this
ages ago that needed revisions.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-05-22 11:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 20:30 Jacek Anaszewski
2019-05-21 21:15 ` Mark Brown
2019-05-22 0:48 ` Dan Murphy
2019-05-22 10:59 ` Mark Brown [this message]
2019-05-22 18:27 ` Jacek Anaszewski
2019-05-22 19:02 ` Mark Brown
2019-05-29 20:44 ` Jacek Anaszewski
2019-05-22 5:42 ` Lee Jones
2019-05-22 19:01 ` Jacek Anaszewski
2019-05-23 8:31 ` Lee Jones
2019-05-23 20:07 ` Jacek Anaszewski
2019-05-24 11:56 ` Mark Brown
2019-05-29 20:44 ` Jacek Anaszewski
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=20190522105958.GA8582@sirena.org.uk \
--to=broonie@kernel.org \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@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
all inboxes | Powered by JetHome®