linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] additional MM updates for 6.19-rc1
Date: Thu, 11 Dec 2025 13:11:27 -0800	[thread overview]
Message-ID: <20251211131127.defed99e5b82e49af605108a@linux-foundation.org> (raw)


Linus, please merge this small batch of followup patches for this -rc
cycle, thanks.

My test merge found no conflicts.



The following changes since commit faf3c923523e5c8fc3baaa413d62e913774ae52f:

  mm: fix vma_start_write_killable() signal handling (2025-11-29 10:41:11 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-stable-2025-12-11-11-39

for you to fetch changes up to dafdba0964bd10913fbaa5537201cbbe05df5b9c:

  mm/damon/tests/core-kunit: avoid damos_test_commit stack warning (2025-12-09 11:25:34 -0800)

----------------------------------------------------------------
Patch series in this pull request:

- The 2 patch series "powerpc/pseries/cmm: two smaller fixes" from David
  Hildenbrand fixes a couple of minor things in ppc land.

- The 4 patch series "Improve folio split related functions" from Zi Yan
  provides some cleanups and minorish fixes in the folio splitting code.

----------------------------------------------------------------
Arnd Bergmann (1):
      mm/damon/tests/core-kunit: avoid damos_test_commit stack warning

Chen Ridong (1):
      mm: vmscan: correct nr_requested tracing in scan_folios

David Hildenbrand (2):
      powerpc/pseries/cmm: call balloon_devinfo_init() also without CONFIG_BALLOON_COMPACTION
      powerpc/pseries/cmm: adjust BALLOON_MIGRATE when migrating pages

Jinhui Guo (1):
      mm/sparse: fix sparse_vmemmap_init_nid_early definition without CONFIG_SPARSEMEM

Lukas Bulwahn (2):
      mm: fix CONFIG_STACK_GROWSUP typo in mm.h
      MAINTAINERS: add idr core-api doc file to XARRAY

Shameer Kolothum (1):
      mm/hugetlb: fix incorrect error return from hugetlb_reserve_pages()

Zi Yan (4):
      mm/huge_memory: change folio_split_supported() to folio_check_splittable()
      mm/huge_memory: replace can_split_folio() with direct refcount calculation
      mm/huge_memory: make min_order_for_split() always return an order
      mm/huge_memory: fix folio split stats counting

 MAINTAINERS                          |   1 +
 arch/powerpc/platforms/pseries/cmm.c |   3 +-
 include/linux/huge_mm.h              |  13 ++-
 include/linux/mm.h                   |   2 +-
 include/linux/mmzone.h               |   2 +-
 mm/damon/tests/core-kunit.h          |   9 +-
 mm/huge_memory.c                     | 165 +++++++++++++++++++----------------
 mm/hugetlb.c                         |  25 ++++--
 mm/vmscan.c                          |   8 +-
 9 files changed, 131 insertions(+), 97 deletions(-)



             reply	other threads:[~2025-12-11 21:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-11 21:11 Andrew Morton [this message]
2025-12-13  9:08 ` 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=20251211131127.defed99e5b82e49af605108a@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