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: linux-mm@kvack.org, mm-commits@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] hotfixes for 6.16
Date: Thu, 24 Jul 2025 18:05:03 -0700	[thread overview]
Message-ID: <20250724180503.a8a80b0b0c904c1c7f967448@linux-foundation.org> (raw)


Linus, please pull this batch of hotfixes, thanks.


The following changes since commit db6cc3f4ac2e6cdc898fc9cbc8b32ae1bf56bdad:

  Revert "sched/numa: add statistics of numa balance task" (2025-07-09 21:07:56 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-hotfixes-stable-2025-07-24-18-03

for you to fetch changes up to 0dec7201788b9152f06321d0dab46eed93834cda:

  sprintf.h requires stdarg.h (2025-07-24 17:58:00 -0700)

----------------------------------------------------------------
11 hotfixes.  9 are cc:stable and the remainder address post-6.15 issues
or aren't considered necessary for -stable kernels.

7 are for MM.

----------------------------------------------------------------
Akinobu Mita (1):
      resource: fix false warning in __request_region()

Harry Yoo (1):
      mm/zsmalloc: do not pass __GFP_MOVABLE if CONFIG_COMPACTION=n

Jason Gunthorpe (1):
      mm: update MAINTAINERS entry for HMM

Jinjiang Tu (1):
      mm/vmscan: fix hwpoisoned large folio handling in shrink_folio_list

Marco Elver (1):
      kasan: use vmalloc_dump_obj() for vmalloc error reports

Nathan Chancellor (1):
      mm/ksm: fix -Wsometimes-uninitialized from clang-21 in advisor_mode_show()

Ryusuke Konishi (1):
      nilfs2: reject invalid file types when reading inodes

SeongJae Park (1):
      mm/damon/core: commit damos_quota_goal->nid

Sergey Senozhatsky (1):
      mailmap: add entry for Senozhatsky

Stephen Rothwell (1):
      sprintf.h requires stdarg.h

Zi Yan (1):
      selftests/mm: fix split_huge_page_test for folio_split() tests

 .mailmap                                          |  4 ++++
 CREDITS                                           |  4 ++++
 MAINTAINERS                                       |  3 ++-
 fs/nilfs2/inode.c                                 |  9 ++++++++-
 include/linux/sprintf.h                           |  1 +
 kernel/resource.c                                 |  5 +++--
 mm/damon/core.c                                   | 15 +++++++++++++++
 mm/kasan/report.c                                 |  4 +++-
 mm/ksm.c                                          |  6 +++---
 mm/memory-failure.c                               |  4 ++++
 mm/vmscan.c                                       |  8 ++++++++
 mm/zsmalloc.c                                     |  3 +++
 tools/testing/selftests/mm/split_huge_page_test.c |  3 ++-
 13 files changed, 60 insertions(+), 9 deletions(-)



             reply	other threads:[~2025-07-25  1:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-25  1:05 Andrew Morton [this message]
2025-07-25  2:50 ` 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=20250724180503.a8a80b0b0c904c1c7f967448@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