From: Mike Rapoport <rppt@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>, Mike Rapoport <rppt@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Thomas Gleixner <tglx@linutronix.de>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
kernel test robot <oliver.sang@intel.com>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org
Subject: [PATCH 0/2] mm: fixes for fallouts from mem_init() cleanup
Date: Tue, 25 Mar 2025 13:49:26 +0200 [thread overview]
Message-ID: <20250325114928.1791109-1-rppt@kernel.org> (raw)
From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
These are the fixes for fallouts from mem_init() cleanup reported by Nathan
Chancellor and kbuild.
The details are in the commit messages.
Mike Rapoport (Microsoft) (2):
mm/mm_init: init holes in the end of the memory map for FLATMEM
memblock: don't release high memory to page allocator when HIGHMEM is off
mm/memblock.c | 3 +++
mm/mm_init.c | 12 ++++++------
2 files changed, 9 insertions(+), 6 deletions(-)
base-commit: 0a1e082b64ccce165e7307a7b49d22b2504f9d1f
--
2.47.2
next reply other threads:[~2025-03-25 11:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 11:49 Mike Rapoport [this message]
2025-03-25 11:49 ` [PATCH 1/2] mm/mm_init: init holes in the end of the memory map for FLATMEM Mike Rapoport
2025-03-25 11:49 ` [PATCH 2/2] memblock: don't release high memory to page allocator when HIGHMEM is off Mike Rapoport
2025-03-26 15:22 ` Nathan Chancellor
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=20250325114928.1791109-1-rppt@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.de \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.