Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 15 May 2023 11:00:57 +0100
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
Message-ID: <20230515100057.GG8963@google.com>
References: <20230511090443.359b120b@canb.auug.org.au>
 <20230511085144.054125a0@aktux>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20230511085144.054125a0@aktux>
Precedence: bulk

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 [李琼斯]