From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the ntfs3 tree
Date: Thu, 11 Sep 2025 19:36:26 -0700 [thread overview]
Message-ID: <20250911193626.8e4568d932a1013ef9c84df9@linux-foundation.org> (raw)
In-Reply-To: <20250912113234.283d8e64@canb.auug.org.au>
On Fri, 12 Sep 2025 11:32:34 +1000 Stephen Rothwell <sfr@canb.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.
next prev parent reply other threads:[~2025-09-12 2:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 1:32 linux-next: duplicate patch in the ntfs3 tree Stephen Rothwell
2025-09-12 2:36 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-15 20:06 Stephen Rothwell
2023-02-16 0:04 ` Tetsuo Handa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250911193626.8e4568d932a1013ef9c84df9@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox