From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Bartosz Golaszewski <brgl@bgdev•pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
William Breathitt Gray <wbg@kernel•org>,
Ioana Ciornei <ioana.ciornei@nxp•com>
Subject: Re: linux-next: duplicate patch in the gpio-brgl tree
Date: Thu, 23 Oct 2025 19:56:21 +1100 [thread overview]
Message-ID: <20251023195621.1ab19cd6@canb.auug.org.au> (raw)
In-Reply-To: <CAMRc=McuH20BpVTLDaEZnrg+uic2byqnPc5VuuDOh59p6fp=dA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
Hi Bartosz,
On Thu, 23 Oct 2025 09:48:25 +0200 Bartosz Golaszewski <brgl@bgdev•pl> wrote:
>
> I had applied this as ae495810cffe to my v6.19 queue earlier into the
> cycle. Then it turned out it's needed in v6.18 as part of a regression
> fix. At this point it was too late for an immutable branch and I
> didn't want to rebase my for-next tree. I decided to just cherry pick
> it into for-current, send it upstream and then pull back v6.18-rc3
> into my for-next and resolve the conflict. Does this work for you?
It's fine. One or 2 duplicated patches don't really matter unless they
cause conflicts. These notifications are mainly just in case you did
it by accident and want to clean it up. (Or to try to dissuade people
from cherry picking things regularly).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-10-23 8:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 1:52 linux-next: duplicate patch in the gpio-brgl tree Stephen Rothwell
2025-10-23 7:48 ` Bartosz Golaszewski
2025-10-23 8:56 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-26 21:17 Stephen Rothwell
2024-02-26 6:41 Stephen Rothwell
2024-02-26 10:02 ` Bartosz Golaszewski
2024-02-26 11:04 ` Lee Jones
2024-02-26 13:37 ` Bartosz Golaszewski
2024-02-26 13:44 ` 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=20251023195621.1ab19cd6@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=brgl@bgdev$(echo .)pl \
--cc=ioana.ciornei@nxp$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=wbg@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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