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: <2025112535-lavish-apple-9cbe@gregkh>
Date: Tue, 25 Nov 2025 08:10:51 +0100
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 Tue, Nov 25, 2025 at 05:17:05PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> The following commit is also in the char-misc.current tree as a different
> commit (but the same patch):
> 
>   8b6322da3c1f ("nvmem: layouts: fix nvmem_layout_bus_uevent")
> 
> This is commit
> 
>   03bc4831ef06 ("nvmem: layouts: fix nvmem_layout_bus_uevent")
> 
> in the char-misc.current tree.

This should be fine, as I was asked to take it in the char-misc tree.

thanks,

greg k-h