From: Corey Minyard <corey@minyard.net>
To: Lee Jones <lee@kernel.org>
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 patches in the mfd-fixes tree
Date: Wed, 5 Nov 2025 06:35:30 -0600 [thread overview]
Message-ID: <aQtEkg6fin70cPVW@mail.minyard.net> (raw)
In-Reply-To: <20251105094750.GF8064@google.com>
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
next prev parent reply other threads:[~2025-11-05 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-26 21:08 linux-next: duplicate patches in the mfd-fixes tree Stephen Rothwell
2025-11-05 9:47 ` Lee Jones
2025-11-05 12:35 ` Corey Minyard [this message]
2025-11-05 15:15 ` 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=aQtEkg6fin70cPVW@mail.minyard.net \
--to=corey@minyard.net \
--cc=lee@kernel.org \
--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.