From: Qiang Ma <maqianga@uniontech.com>
To: akpm@linux-foundation.org, bhe@redhat.com,
catalin.marinas@arm.com, will@kernel.org
Cc: kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Qiang Ma <maqianga@uniontech.com>
Subject: [PATCH v1 3/3] arm64: kexec: Adjust the debug print of kexec_image_info
Date: Fri, 12 Dec 2025 17:56:49 +0800 [thread overview]
Message-ID: <20251212095649.857796-4-maqianga@uniontech.com> (raw)
In-Reply-To: <20251212095649.857796-1-maqianga@uniontech.com>
In the previous patch, we move start/head of kimage to the
generic code, so, we remove them to avoid duplicate printing.
Signed-off-by: Qiang Ma <maqianga@uniontech.com>
---
arch/arm64/kernel/machine_kexec.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm64/kernel/machine_kexec.c b/arch/arm64/kernel/machine_kexec.c
index 239c16e3d02f..0896e3e6a811 100644
--- a/arch/arm64/kernel/machine_kexec.c
+++ b/arch/arm64/kernel/machine_kexec.c
@@ -34,8 +34,6 @@ static void _kexec_image_info(const char *func, int line,
{
kexec_dprintk("%s:%d:\n", func, line);
kexec_dprintk(" kexec kimage info:\n");
- kexec_dprintk(" type: %d\n", kimage->type);
- kexec_dprintk(" head: %lx\n", kimage->head);
kexec_dprintk(" kern_reloc: %pa\n", &kimage->arch.kern_reloc);
kexec_dprintk(" el2_vectors: %pa\n", &kimage->arch.el2_vectors);
}
--
2.20.1
prev parent reply other threads:[~2025-12-12 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 9:56 [PATCH v1 0/3] kexec: add kexec flag to control debug printing Qiang Ma
2025-12-12 9:56 ` [PATCH v1 1/3] " Qiang Ma
2025-12-12 9:56 ` [PATCH v1 2/3] kexec: print out debugging message if required for kexec_load Qiang Ma
2025-12-15 0:32 ` Andrew Morton
2025-12-15 4:41 ` Qiang Ma
2025-12-12 9:56 ` Qiang Ma [this message]
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=20251212095649.857796-4-maqianga@uniontech.com \
--to=maqianga@uniontech.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will@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