linux-kernel - Re: linux-next: duplicate patch in the ntfs3 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] [day] [month] [year] [list]

Message-Id: <20250911193626.8e4568d932a1013ef9c84df9@linux-foundation.org>
Date: Thu, 11 Sep 2025 19:36:26 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Konstantin Komarov <almaz.alexandrovich@...agon-software.com>, 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 ntfs3 tree

On Fri, 12 Sep 2025 11:32:34 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> Hi all,
> 
> The following commit is also in the mm-unstable tree as a different commit
> (but the same patch):
> 
>   7d460636b640 ("ntfs3: stop using write_cache_pages")
> 
> This is commit
> 
>   5c059d9d0947 ("ntfs3: stop using write_cache_pages")
> 
> in the mm-unstable tree wher it is part of series.

Well that's annoying.  I am to redo the series to pretend that this
patch was not part of it?  A simple acked-by would have been so much
more straightforward.

I think I"ll retain the series as-is.  git will sort it out.

> BTW, Andrew, in mm-unstable "mm: remove write_cache_pages" and "bcachefs:
> stop using write_cache_pages" appear to be in the wrong order?

Ah, thanks, fixed.