From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: linux-mm@kvack.org, mm-commits@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] hotfixes for 7.0-rc5
Date: Mon, 16 Mar 2026 12:17:27 -0700 [thread overview]
Message-ID: <20260316121727.54468f0e01ca280c17f2b735@linux-foundation.org> (raw)
Linus, please merge this batch of hotfixes, thanks.
The following changes since commit b4f0dd314b39ea154f62f3bd3115ed0470f9f71e:
Merge tag 'mm-hotfixes-stable-2026-03-09-16-36' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm (2026-03-10 12:47:56 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-hotfixes-stable-2026-03-16-12-15
for you to fetch changes up to 182b9b3d8d1d36500f58e4f3dc82b144d6487bdf:
MAINTAINERS: update email address for Ignat Korchagin (2026-03-10 16:01:49 -0700)
----------------------------------------------------------------
6 hotfixes. 4 are cc:stable. 3 are for MM.
All are singletons - please see the changelogs for details.
----------------------------------------------------------------
Chris Down (1):
mm/huge_memory: fix use of NULL folio in move_pages_huge_pmd()
Dev Jain (1):
mm/rmap: fix incorrect pte restoration for lazyfree folios
Ignat Korchagin (1):
MAINTAINERS: update email address for Ignat Korchagin
Randy Dunlap (1):
build_bug.h: correct function parameters names in kernel-doc
Thorsten Blum (1):
crash_dump: don't log dm-crypt key bytes in read_key_from_user_keying
Wei Yang (1):
mm/huge_memory: fix early failure try_to_migrate() when split huge pmd for shared THP
.mailmap | 1 +
MAINTAINERS | 8 ++++----
include/linux/build_bug.h | 4 +++-
kernel/crash_dump_dm_crypt.c | 4 ++--
mm/huge_memory.c | 3 ++-
mm/rmap.c | 21 +++++++++++++++++----
6 files changed, 29 insertions(+), 12 deletions(-)
next reply other threads:[~2026-03-16 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 19:17 Andrew Morton [this message]
2026-03-17 20:57 ` pr-tracker-bot
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=20260316121727.54468f0e01ca280c17f2b735@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@linuxfoundation.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