linux-kernel - Re: linux-next: duplicate patch in the nvmem tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2025071443-humbling-paddling-a4de@gregkh>
Date: Mon, 14 Jul 2025 09:51:10 +0200
From: Greg KH <greg@...ah.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Srinivas Kandagatla <srini@...nel.org>, Arnd Bergmann <arnd@...db.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the nvmem tree

On Mon, Jul 14, 2025 at 05:34:46PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> The following commit is also in the char-misc.current tree as a different
> commit (but the same patch):
> 
>   d102a7924f44 ("nvmem: imx-ocotp: fix MAC address byte length")
> 
> This is commit
> 
>   2aa4ad626ee7 ("nvmem: imx-ocotp: fix MAC address byte length")
> 
> in the char-misc.current tree.

That's due to the nvmem tree sending them to me in patch format.  Should
be fine, thanks!

greg k-h