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 patch in the regulator tree
Date: Thu, 8 Jun 2023 13:42:30 +0100 [thread overview]
Message-ID: <20230608124230.GH1930705@google.com> (raw)
In-Reply-To: <38913e8e-4578-4c4f-a6cd-6f6e628957af@sirena.org.uk>
On Wed, 07 Jun 2023, Mark Brown wrote:
> On Wed, Jun 07, 2023 at 04:37:43PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > The following commit is also in the mfd tree as a different commit
> > (but the same patch):
> >
> > 75c8cb2f4cb2 ("mfd: axp20x: Add support for AXP313a PMIC")
> >
> > This is commit
> >
> > 2f518d914bd3 ("mfd: axp20x: Add support for AXP313a PMIC")
> >
> > in the mfd tree.
>
> Hrm, that was a tag I pulled from Lee rather than something I applied -
> not sure what's going on there.
Mea culpa. I hadn't rebased onto my own tag.
Should be fixed in the next -next cut.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-06-08 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 6:37 linux-next: duplicate patch in the regulator tree Stephen Rothwell
2023-06-07 11:29 ` Mark Brown
2023-06-08 12:42 ` Lee Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-01 5:42 Stephen Rothwell
2025-02-19 2:43 Stephen Rothwell
2025-02-23 8:27 ` Shawn Guo
2025-02-24 16:01 ` Mark Brown
2025-02-25 0:37 ` Shawn Guo
2025-02-25 13:37 ` Mark Brown
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=20230608124230.GH1930705@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.