From: Mike Rapoport <rppt@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@kernel.org>,
Pratyush Brahma <pratyush.brahma@oss.qualcomm.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] memblock fixes for v6.17-rc4
Date: Thu, 28 Aug 2025 08:35:23 +0300 [thread overview]
Message-ID: <aK_qmw51CJz_Tz36@kernel.org> (raw)
Hi Linus,
The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock tags/fixes-2025-08-28
for you to fetch changes up to b3dcc9d1d806fb1e175f85978713eef868531da4:
memblock: fix kernel-doc for MEMBLOCK_RSRV_NOINIT (2025-08-26 10:47:03 +0300)
----------------------------------------------------------------
memblock fixes for v6.17-rc4
* printk cleanups in memblock and numa_memblks
* update kernel-doc for MEMBLOCK_RSRV_NOINIT to be more accurate and
detailed
----------------------------------------------------------------
Mike Rapoport (Microsoft) (1):
memblock: fix kernel-doc for MEMBLOCK_RSRV_NOINIT
Pratyush Brahma (2):
mm/numa_memblks: Use pr_debug instead of printk(KERN_DEBUG)
mm: numa,memblock: Use SZ_1M macro to denote bytes to MB conversion
include/linux/memblock.h | 5 +++--
mm/memblock.c | 19 +++++++++++++------
mm/numa_emulation.c | 4 ++--
mm/numa_memblks.c | 6 +++---
4 files changed, 21 insertions(+), 13 deletions(-)
--
Sincerely yours,
Mike.
next reply other threads:[~2025-08-28 5:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 5:35 Mike Rapoport [this message]
2025-08-29 16:39 ` [GIT PULL] memblock fixes for v6.17-rc4 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=aK_qmw51CJz_Tz36@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pratyush.brahma@oss.qualcomm.com \
--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;
as well as URLs for NNTP newsgroup(s).