From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-mm@kvack.org, mm-commits@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Additional MM updates for 6.16-rc1
Date: Mon, 2 Jun 2025 12:17:51 -0700 [thread overview]
Message-ID: <20250602121751.53ee502779a2f746404a3548@linux-foundation.org> (raw)
In-Reply-To: <aD29wnb5zR-afWpM@casper.infradead.org>
On Mon, 2 Jun 2025 16:05:38 +0100 Matthew Wilcox <willy@infradead.org> wrote:
> On Sun, Jun 01, 2025 at 03:12:22PM -0700, Andrew Morton wrote:
> > Linus, please merge this second batch of MM updates for the 6.16-rcX cycle.
>
> A word of warning for Linus since he wouldn't've been cc'd on the
> earlier email. This branch is based on v6.15-rc6 but contains a
> commit which depends on 97dfbbd135cb which was merged during the
> current merge window. You might want to do a rebase or ask Andrew to
> do it in order to prevent a bisection hazard.
>
> 0day-ci found the problem here:
> https://lore.kernel.org/linux-mm/202506022027.IYQzZghL-lkp@intel.com/
I think it's OK? I did the merge and
d9736929445e iov: remove copy_page_from_iter_atomic()
lands later than
97dfbbd135cb highmem: add folio_test_partial_kmap()
next prev parent reply other threads:[~2025-06-02 19:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-01 22:12 Andrew Morton
2025-06-02 15:05 ` Matthew Wilcox
2025-06-02 19:17 ` Andrew Morton [this message]
2025-06-02 19:20 ` Matthew Wilcox
2025-06-02 23:03 ` Linus Torvalds
2025-06-10 9:05 ` Geert Uytterhoeven
2025-06-10 15:54 ` Andrew Morton
2025-06-10 16:41 ` Geert Uytterhoeven
2025-06-10 17:04 ` SeongJae Park
2025-06-10 17:27 ` Linus Torvalds
2025-06-10 17:32 ` SeongJae Park
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=20250602121751.53ee502779a2f746404a3548@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.org \
/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