From: Dave Hansen <dave.hansen@intel.com>
To: Brendan Jackman <jackmanb@google.com>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] x86/mm: drop unused return from init_memory_mapping()
Date: Tue, 2 Jun 2026 14:30:36 -0700 [thread overview]
Message-ID: <1f53ea76-dca6-47fa-bafa-264496fee632@intel.com> (raw)
In-Reply-To: <20260503-x86-init-cleanup-v2-1-bb690bd2477c@google.com>
On 5/3/26 06:04, Brendan Jackman wrote:
> None of the callers look at the return value.
Ahh, yes. Looks like once upon a time it was used to set max_pfn_mapped.
But, at some point add_pfn_range_mapped() started doing it instead.
Reviewed-by: Dave Hansen <dave.hansen@linux.intel.com>
next prev parent reply other threads:[~2026-06-02 21:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-03 13:04 [PATCH v2 0/3] x86/mm: some cleanups for pagetable setup code Brendan Jackman
2026-05-03 13:04 ` [PATCH v2 1/3] x86/mm: drop unused return from init_memory_mapping() Brendan Jackman
2026-06-02 21:30 ` Dave Hansen [this message]
2026-05-03 13:04 ` [PATCH v2 2/3] x86/mm: simplify calculation of max_pfn_mapped Brendan Jackman
2026-06-02 21:39 ` Dave Hansen
2026-06-03 10:20 ` Brendan Jackman
2026-05-03 13:04 ` [PATCH v2 3/3] x86/mm: drop unused returns from direct map setup functions Brendan Jackman
2026-06-02 21:40 ` Dave Hansen
2026-05-27 12:40 ` [PATCH v2 0/3] x86/mm: some cleanups for pagetable setup code Brendan Jackman
2026-06-02 21:53 ` Dave Hansen
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=1f53ea76-dca6-47fa-bafa-264496fee632@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jackmanb@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@kernel.org \
--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.