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] additional MM updates for 6.18-rc1
Date: Sun, 5 Oct 2025 11:15:38 -0700 [thread overview]
Message-ID: <20251005111538.3996dae46662e46054d46528@linux-foundation.org> (raw)
Linus, please merge this small and final batch of MM updates for the
6.18-rc development cycle.
No conflicts are seen or anticipated.
Thanks.
The following changes since commit 1367da7eb875d01102d2ed18654b24d261ff5393:
mm: swap: check for stable address space before operating on the VMA (2025-09-28 11:51:34 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-stable-2025-10-03-16-49
for you to fetch changes up to c14bdcc9f274620492aba7d920cc2641440cf1ba:
mm/khugepaged: use KMEM_CACHE() (2025-10-03 16:42:44 -0700)
----------------------------------------------------------------
Only two patch series in this pull request:
- The 3 patch series "mm/memory_hotplug: fixup crash during uevent
handling" from Hannes Reinecke which fixes a race which was causing udev
to trigger a crash in the memory hotplug code.
- The 2 patch series "mm_slot: following fixup for usage of
mm_slot_entry()" from Wei Yang adds some touchups to the just-merged
mm_slot changes.
----------------------------------------------------------------
Anshuman Khandual (1):
Documentation/mm: drop pxx_mkdevmap() descriptions from page table helpers
Hannes Reinecke (3):
drivers/base/memory: add node id parameter to add_memory_block()
mm/memory_hotplug: activate node before adding new memory blocks
drivers/base: move memory_block_add_nid() into the caller
Lance Yang (1):
mm: clean up is_guard_pte_marker()
Wei Yang (2):
mm/ksm: cleanup mm_slot_entry() invocation
mm/khugepaged: use KMEM_CACHE()
Documentation/mm/arch_pgtable_helpers.rst | 6 ----
drivers/base/memory.c | 53 ++++++++++++++-----------------
drivers/base/node.c | 10 +++---
include/linux/memory.h | 5 ++-
mm/khugepaged.c | 5 +--
mm/ksm.c | 27 ++++++++--------
mm/madvise.c | 4 +--
mm/memory_hotplug.c | 32 ++++++++++---------
8 files changed, 63 insertions(+), 79 deletions(-)
next reply other threads:[~2025-10-05 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-05 18:15 Andrew Morton [this message]
2025-10-05 19:45 ` 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=20251005111538.3996dae46662e46054d46528@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