From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-mm@kvack.org, mm-commits@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] additional non-MM updates for 6.18-rc1
Date: Fri, 10 Oct 2025 15:08:44 -0700 [thread overview]
Message-ID: <20251010150844.1ac58a5f9b89aa1e7e260ace@linux-foundation.org> (raw)
Linus, please merge this small and final batch of non-MM changes for
this merge cycle, thanks.
The following changes since commit 7a405dbb0f036f8d1713ab9e7df0cd3137987b07:
Merge tag 'mm-stable-2025-10-03-16-49' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm (2025-10-05 12:11:07 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-nonmm-stable-2025-10-10-15-03
for you to fetch changes up to 90eb9ae35727a662789c850efaf225ffe5511fae:
lib/test_kho: use kho_preserve_vmalloc instead of storing addresses in fdt (2025-10-07 13:48:56 -0700)
----------------------------------------------------------------
Just one series here - Mike Rappoport has taught KEXEC handover to
preserve vmalloc allocations across handover.
----------------------------------------------------------------
Mike Rapoport (Microsoft) (4):
kho: check if kho is finalized in __kho_preserve_order()
kho: replace kho_preserve_phys() with kho_preserve_pages()
kho: add support for preserving vmalloc allocations
lib/test_kho: use kho_preserve_vmalloc instead of storing addresses in fdt
Umang Jain (1):
MAINTAINERS, .mailmap: update Umang's email address
.mailmap | 1 +
MAINTAINERS | 2 +-
include/linux/kexec_handover.h | 33 +++-
kernel/kexec_handover.c | 361 ++++++++++++++++++++++++++++++++++++-----
lib/test_kho.c | 41 +++--
mm/memblock.c | 4 +-
6 files changed, 383 insertions(+), 59 deletions(-)
next reply other threads:[~2025-10-10 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 22:08 Andrew Morton [this message]
2025-10-11 18:37 ` 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=20251010150844.1ac58a5f9b89aa1e7e260ace@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 \
/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
all inboxes | Powered by JetHome®