From: Lee Jones <lee@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Liam Girdwood <lgirdwood@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the regulator tree
Date: Fri, 25 Oct 2024 09:51:46 +0100 [thread overview]
Message-ID: <20241025085146.GB10824@google.com> (raw)
In-Reply-To: <ef8697e9-9eb1-459f-8c5d-197019029fbc@sirena.org.uk>
On Tue, 22 Oct 2024, Mark Brown wrote:
> On Wed, Oct 16, 2024 at 02:09:24PM +0100, Lee Jones wrote:
>
> > I said to apply the regulator patch because it looked like it didn't
> > have any dependencies. The latter part was my mistake as now I see that
> > it did have deps.
>
> I've now dropped those patches.
Thanks Mark, I appreciate that.
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2024-10-25 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 2:59 linux-next: duplicate patches in the regulator tree Stephen Rothwell
2024-10-16 7:55 ` Lee Jones
2024-10-16 11:33 ` Mark Brown
2024-10-16 13:09 ` Lee Jones
2024-10-22 20:03 ` Mark Brown
2024-10-25 8:51 ` Lee Jones [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=20241025085146.GB10824@google.com \
--to=lee@kernel.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.