From: Baoquan He <bhe@redhat.com>
To: linux-kernel@vger.kernel.org, mingo@kernel.org, bp@alien8.de,
thomas.lendacky@amd.com
Cc: x86@kernel.org, Baoquan He <bhe@redhat.com>
Subject: [PATCH v2 0/2] x86/ioremap: clean up the mess in xxx_is_setup_data
Date: Mon, 18 Nov 2024 09:08:17 +0800 [thread overview]
Message-ID: <20241118010819.46602-1-bhe@redhat.com> (raw)
Functions memremap_is_setup_data() and early_memremap_is_setup_data()
share completely the same process and handling, except of the
different memremap/unmap invocations. The code can be extracted and put
into a helper function __memremap_is_setup_data().
And parameter 'size' is unused in implementation of memremap_is_efi_data(),
memremap_is_setup_data and early_memremap_is_setup_data().
This patchset is made to clean them up. It sits on top of tip/x86/urgent
commit 8d9ffb2fe65a ("x86/mm: Fix a kdump kernel failure on SME system
when CONFIG_IMA_KEXEC=y")
v1->v2:
- Remove __init from helper __memremap_is_setup_data(), add __ref to
helper suppress mismatch section warning.
- Merge the old patch 1 and 2 into one patch.
- Both are suggested by Tom during reviewing. Thanks to him.
Baoquan He (2):
x86/ioremap: introduce helper to implement xxx_is_setup_data()
x86/mm: clean up unused parameters of functions
arch/x86/mm/ioremap.c | 117 +++++++++++++++---------------------------
1 file changed, 41 insertions(+), 76 deletions(-)
--
2.41.0
next reply other threads:[~2024-11-18 1:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 1:08 Baoquan He [this message]
2024-11-18 1:08 ` [PATCH v2 1/2] x86/ioremap: introduce helper to implement xxx_is_setup_data() Baoquan He
2024-11-18 15:19 ` Tom Lendacky
2024-11-19 3:07 ` Baoquan He
2024-11-19 10:55 ` Ingo Molnar
2024-11-20 7:21 ` Baoquan He
2024-11-20 7:56 ` Baoquan He
2024-11-20 8:25 ` Ingo Molnar
2024-11-20 14:14 ` Tom Lendacky
2024-11-25 9:07 ` Ingo Molnar
2024-11-26 8:15 ` Baoquan He
2024-11-18 1:08 ` [PATCH v2 2/2] x86/mm: clean up unused parameters of functions Baoquan He
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=20241118010819.46602-1-bhe@redhat.com \
--to=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=thomas.lendacky@amd.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox