[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <627cbb55-2a55-4124-8f6e-7b4ba0441558@csgroup.eu>
Date: Wed, 30 Jul 2025 15:41:48 +0200
From: Christophe Leroy <christophe.leroy@...roup.eu>
To: Arnd Bergmann <arnd@...db.de>, Bartosz Golaszewski <brgl@...ev.pl>
Cc: ARM <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the fsl tree
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
Powered by blists - more mailing lists