[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aQtEkg6fin70cPVW@mail.minyard.net>
Date: Wed, 5 Nov 2025 06:35:30 -0600
From: Corey Minyard <corey@...yard.net>
To: Lee Jones <lee@...nel.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patches in the mfd-fixes tree
On Wed, Nov 05, 2025 at 09:47:50AM +0000, Lee Jones wrote:
> On Mon, 27 Oct 2025, Stephen Rothwell wrote:
>
> > Hi all,
> >
> > The following commits are also in Linus Torvalds' tree as different
> > commits (but the same patches):
> >
> > 91a3e1f5453a ("mfd: ls2kbmc: Check for devm_mfd_add_devices() failure")
> > fdff3cadeea9 ("mfd: ls2kbmc: Fix an IS_ERR() vs NULL check in probe()")
> >
> > These are commits
> >
> > 4af66c2bcab0 ("mfd: ls2kbmc: check for devm_mfd_add_devices() failure")
> > 0892507f4a0b ("mfd: ls2kbmc: Fix an IS_ERR() vs NULL check in probe()")
> >
> > in Linus' tree.
>
> This is because Corey applied patches that they shouldn't have done,
> despite being expressively requested not to!
>
> https://lore.kernel.org/all/20251009095611.GC8757@google.com/
I missed this completely, I'm sorry.
If there's anything I can do to fix this, I will, but I'm not sure what
is best now.
-corey
Powered by blists - more mailing lists