From: Thorsten Blum <blum@kernel.org>
To: Mike Rapoport <rppt@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
Alexander Graf <graf@amazon.com>, Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>,
Changyuan Lyu <changyuanl@google.com>
Cc: Thorsten Blum <blum@kernel.org>,
kexec@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2] kho: Remove redundant 0x prefixes
Date: Wed, 4 Nov 2026 17:23:53 +0100 [thread overview]
Message-ID: <20261104162352.140836-3-blum@kernel.org> (raw)
The %pa format specifier already includes the 0x prefix. Remove the
redundant prefixes to avoid printing 0x0x.
Use phys_addr_t for size to match the expected type.
Fixes: c609c144b0e8 ("kexec: add KHO parsing support")
Signed-off-by: Thorsten Blum <blum@kernel.org>
---
Changes in v2:
- Use phys_addr_t for size as suggested by Arnd (thanks!)
- v1: https://lore.kernel.org/r/20261104160931.137174-3-blum@kernel.org/
kernel/liveupdate/kexec_handover.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/kernel/liveupdate/kexec_handover.c b/kernel/liveupdate/kexec_handover.c
index 6f1f55fe3181..6a7600a0a7d5 100644
--- a/kernel/liveupdate/kexec_handover.c
+++ b/kernel/liveupdate/kexec_handover.c
@@ -2010,16 +2010,16 @@ void __init kho_populate(phys_addr_t fdt_phys, u64 fdt_len,
*/
for (int i = 0; i < bootmem_cnt; i++) {
struct kho_bootmem *area = &bootmem[i];
- u64 size = area->size;
+ phys_addr_t size = area->size;
memblock_add(area->addr, size);
err = memblock_mark_kho_noprsrv(area->addr, size);
if (err) {
- pr_warn("failed to mark the bootmem region 0x%pa+0x%pa: %pe",
+ pr_warn("failed to mark the bootmem region %pa+%pa: %pe",
&area->addr, &size, ERR_PTR(err));
goto unmap_bootmem;
}
- pr_debug("Marked 0x%pa+0x%pa as bootmem", &area->addr, &size);
+ pr_debug("Marked %pa+%pa as bootmem", &area->addr, &size);
}
memblock_reserve(bootmem_phys, bootmem_len);
next reply other threads:[~2026-11-04 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 16:23 Thorsten Blum [this message]
2026-11-04 16:28 ` Arnd Bergmann
2026-11-04 20:55 ` Pasha Tatashin
2026-11-04 20:59 ` Arnd Bergmann
2026-11-04 21:52 ` Pasha Tatashin
2026-11-04 22:06 ` Pasha Tatashin
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=20261104162352.140836-3-blum@kernel.org \
--to=blum@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=changyuanl@google.com \
--cc=graf@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@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
all inboxes | Powered by JetHome®