mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Arnd Bergmann <arnd@arndb.de>, Bartosz Golaszewski <brgl@bgdev.pl>
Cc: ARM <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the fsl tree
Date: Wed, 30 Jul 2025 15:41:48 +0200	[thread overview]
Message-ID: <627cbb55-2a55-4124-8f6e-7b4ba0441558@csgroup.eu> (raw)
In-Reply-To: <20250723094558.5bcfca69@canb.auug.org.au>

Hi all,

Le 23/07/2025 à 01:45, Stephen Rothwell a écrit :
> Hi all,
> 
> The following commit is also in the arm-soc tree as a different commit
> (but the same patch):
> 
>    8b3da0519ae6 ("soc: fsl: qe: convert set_multiple() to returning an integer")
> 
> This is commit
> 
>    12702f0c3834 ("soc: fsl: qe: convert set_multiple() to returning an integer")
> 
> in the arm-soc tree.
> 


I was going to send a pull request for this fix but I see the duplicate 
patch is already tagged in the soc tree:

$ git tag --contains 12702f0c3834
next-20250728
next-20250730
soc-drivers-6.17

Shall I do anything or just ignore it and drop it from my tree ?

Thanks
Christophe

  reply	other threads:[~2025-07-30 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-22 23:45 Stephen Rothwell
2025-07-30 13:41 ` Christophe Leroy [this message]
2025-07-30 13:55   ` Arnd Bergmann
2025-07-30 14:23     ` Christophe Leroy
2025-07-30 14:37       ` Bartosz Golaszewski
2025-07-30 18:45       ` Arnd Bergmann
2025-08-12  1:03 ` Stephen Rothwell

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=627cbb55-2a55-4124-8f6e-7b4ba0441558@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=arnd@arndb.de \
    --cc=brgl@bgdev.pl \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®