From: Lee Jones <lee@kernel.org>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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 leds-lj tree
Date: Mon, 15 May 2023 11:00:57 +0100 [thread overview]
Message-ID: <20230515100057.GG8963@google.com> (raw)
In-Reply-To: <20230511085144.054125a0@aktux>
On Thu, 11 May 2023, Andreas Kemnade wrote:
> On Thu, 11 May 2023 09:04:43 +1000
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > Hi all,
> >
> > The following commit is also in Linus Torvalds' tree as a `different
> > commit (but the same patch):
> >
> > fea27b037127 ("leds: bd2606mvv: Driver for the Rohm 6 Channel i2c LED driver")
> >
> > This is commit
> >
> > 8325642d2757 ("leds: bd2606mvv: Driver for the Rohm 6 Channel i2c LED driver")
> >
> BTW: and also:
>
> 3808b8424b476 ("leds: bd2606mvv: Driver for the Rohm 6 Channel i2c LED driver")
>
> it went in probably by accident through both led and mfd pull requests for 6.4.
And now it's queued up again.
Sounds like it's definitely going to be applied then.
Must be a good patch. :)
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-05-15 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 23:04 linux-next: duplicate patch in the leds-lj tree Stephen Rothwell
2023-05-11 6:51 ` Andreas Kemnade
2023-05-15 10:00 ` Lee Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-12 4:01 Stephen Rothwell
2024-04-12 7:09 ` 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=20230515100057.GG8963@google.com \
--to=lee@kernel.org \
--cc=andreas@kemnade.info \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).