linux-kernel - Re: linux-next: duplicate patches in the vfs-brauner 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 for Android: free password hash cracker in your pocket

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

Date: Wed, 3 Apr 2024 19:09:27 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Christian Brauner <brauner@...nel.org>, Dominique Martinet
 <asmadeus@...ewreck.org>, Arnd Bergmann <arnd@...db.de>, Randy Dunlap
 <rdunlap@...radead.org>, Linux Kernel Mailing List
 <linux-kernel@...r.kernel.org>, Linux Next Mailing List
 <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patches in the vfs-brauner tree

On Thu, 4 Apr 2024 10:10:38 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> The following commits are also in the mm and v9fs trees as different
> commits (but the same patches):
> 
>   0e74485c814a ("nilfs2: fix out-of-range warning")
>   528aa74c091d ("9p: Clean up a kdoc warning.")
> 
> These are commit
> 
>   93df85cc09a2 ("nilfs2: fix out-of-range warning")
> 
> from the mm-non-mm-unstable branch of the mm tree

Thanks, I'll drop that patch from mm.git.