From: Baoquan He <bhe@redhat.com>
To: Askar Safin <safinaskar@zohomail.com>
Cc: Simon Horman <horms@kernel.org>,
Jeremy Linton <jeremy.linton@arm.com>,
kexec <kexec@lists.infradead.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [PATCH v4 0/6] Fix printf string specifiers, otherwise kexec doesn't work on my laptop
Date: Tue, 23 Sep 2025 10:15:19 +0800 [thread overview]
Message-ID: <aNICt3e3Fg0iwxvv@MiWiFi-R3L-srv> (raw)
In-Reply-To: <19972b2566e.1115458b7339833.495097856732093802@zohomail.com>
On 09/22/25 at 10:31pm, Askar Safin wrote:
> Simon Horman, so what? This patchset is still not merged.
Not sure if Simon minds the patch log, especially in patch 1. I saw the
'TL;DR' first time in a patch log.
For a problem solving patch, we better provide information like
-what is the problem;
-why it's caused;
-how you fix it;
Don't tell too long story out of the space. Refering to other already
merged commit's log is also a good way to learn that.
The fix is absolutely a great one.
Thanks
Baoquan
next prev parent reply other threads:[~2025-09-23 2:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 21:30 [PATCH v4 0/6] Fix printf string specifiers, otherwise kexec doesn't work on my laptop Askar Safin
2025-08-19 21:30 ` [PATCH v4 1/6] " Askar Safin
2025-08-19 21:30 ` [PATCH v4 2/6] kexec/kexec-elf-exec.c: Replace %lux with %lx Askar Safin
2025-08-19 21:30 ` [PATCH v4 3/6] kexec/arch/i386/x86-linux-setup.c: replace %d with %u Askar Safin
2025-08-19 21:30 ` [PATCH v4 4/6] util_lib/elf_info.c: fix typo: prink -> printk Askar Safin
2025-08-19 21:30 ` [PATCH v4 5/6] kexec/arch/i386/kexec-x86-common.c: remove duplicate <stdio.h> Askar Safin
2025-08-19 21:30 ` [PATCH v4 6/6] kexec/arch/arm64/crashdump-arm64.c: remove extra whitespace Askar Safin
2025-09-22 18:31 ` [PATCH v4 0/6] Fix printf string specifiers, otherwise kexec doesn't work on my laptop Askar Safin
2025-09-23 2:15 ` Baoquan He [this message]
2025-09-23 13:56 ` Simon Horman
2025-09-26 21:09 ` Jeremy Linton
2025-09-29 9:50 ` Simon Horman
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=aNICt3e3Fg0iwxvv@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=andy.shevchenko@gmail.com \
--cc=horms@kernel.org \
--cc=jeremy.linton@arm.com \
--cc=kexec@lists.infradead.org \
--cc=safinaskar@zohomail.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 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.