public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Qiang Ma <maqianga@uniontech.com>
Cc: akpm@linux-foundation.org, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] kexec: print out debugging message if required for kexec_load
Date: Thu, 27 Nov 2025 10:36:13 +0800	[thread overview]
Message-ID: <aSe5HXpBtzLnHvNG@MiWiFi-R3L-srv> (raw)
In-Reply-To: <63BA9935197ADF34+2a3faf95-36da-46f1-b9b5-4e438e75d1be@uniontech.com>

On 11/27/25 at 10:04am, Qiang Ma wrote:
> 
> 在 2025/11/27 09:47, Baoquan He 写道:
> > Hi,
> > 
> > On 11/26/25 at 04:44pm, Qiang Ma wrote:
> > > Overview:
> > > =========
> > > The commit a85ee18c7900 ("kexec_file: print out debugging message
> > > if required") has added general code printing in kexec_file_load(),
> > > but not in kexec_load().
> > > Since kexec_load and kexec_file_load are not triggered simultaneously,
> > > we can unify the debug flag of kexec and kexec_file as kexec_dbg_print.
> > As I said in your last post, this is not needed at all, you just add a
> > not needed thing to kernel.
> > 
> > So NACK this patchset, unless you have reason to justify it. Sorry about
> > it.
> The segment prints discussed in the last post,
> 
> this patchset has been removed, leaving only type/start/head of kimage and
> flags.
> 
> 
> I think the current patchset is still necessary.
> For example, renaming kexec_file_dbg_print is still necessary, but not for
> kexec_file.

How come renaming kexec_file_dbg_print is a justification in this case.

No, kexec_file_dbg_print is named because it's only for kexec_file
debugging printing. Because we have had enough debugging printing for
kexec_load interface. Do you have difficulty on debugging printing of
kexec_load? 


  reply	other threads:[~2025-11-27  2:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26  8:44 [PATCH v3 0/3] kexec: print out debugging message if required for kexec_load Qiang Ma
2025-11-26  8:44 ` [PATCH v3 1/3] kexec: Fix uninitialized struct kimage *image pointer Qiang Ma
2025-11-26  8:44 ` [PATCH v3 2/3] kexec: add kexec flag to control debug printing Qiang Ma
2025-11-26  8:44 ` [PATCH v3 3/3] kexec: print out debugging message if required for kexec_load Qiang Ma
2025-11-27  1:47 ` [PATCH v3 0/3] " Baoquan He
2025-11-27  2:04   ` Qiang Ma
2025-11-27  2:36     ` Baoquan He [this message]
2025-11-27  3:00       ` Qiang Ma
2025-11-27  3:55         ` Baoquan He
2025-11-27  6:59           ` Qiang Ma
2025-11-27 12:01 ` Sourabh Jain
2025-11-27 15:30   ` Baoquan He
2025-11-28  9:41     ` Sourabh Jain
2025-11-30  2:56       ` Baoquan He
2025-12-04 12:18 ` Sourabh Jain
2025-12-05  9:20   ` Qiang Ma
2025-12-09  0:45   ` 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=aSe5HXpBtzLnHvNG@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maqianga@uniontech.com \
    /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