From: " donmor" <donmor3000@hotmail.com>
To: "Markus.Elfring@web.de" <Markus.Elfring@web.de>,
"chenhuacai@kernel.org" <chenhuacai@kernel.org>,
"kernel@xen0n.name" <kernel@xen0n.name>
Cc: "kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"jiaxun.yang@flygoat.com" <jiaxun.yang@flygoat.com>,
"loongarch@lists.linux.dev" <loongarch@lists.linux.dev>,
"chenhuacai@loongson.cn" <chenhuacai@loongson.cn>,
"guoren@kernel.org" <guoren@kernel.org>,
"lixuefeng@loongson.cn" <lixuefeng@loongson.cn>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"loongson-kernel@lists.loongnix.cn"
<loongson-kernel@lists.loongnix.cn>
Subject: Re: [PATCH v5] LoongArch: Fix CONFIG_CMDLINE_EXTEND and CONFIG_CMDLINE_BOOTLOADER handling
Date: Thu, 20 Jul 2023 01:34:55 +0000 [thread overview]
Message-ID: <281c5d5e51488ce51497072c1e4304d71af141ec.camel@hotmail.com> (raw)
In-Reply-To: <f9e7fb54-a76e-a9b0-1b9c-8c9251f4af20@xen0n.name>
在 2023-07-19星期三的 18:29 +0800,WANG Xuerui写道:
> On 2023/7/19 15:22, Huacai Chen wrote:
> > Hi, Markus,
> >
> > On Wed, Jul 19, 2023 at 2:51 PM Markus Elfring <Markus.Elfring@web.de> wrote:
> > > > …, so this patch add
> > > > some code to fix it.
> > >
> > > Would you like to avoid a typo here?
> > >
> > > Will any other imperative change description variant become more helpful?
> > Thank you for pointing this out, but since Zhihong is the original
> > author, I don't want to completely rewrite the commit message, so just
> > fix the typo...
>
> AFAICT the commit message is totally uninformative even if "an
> imperative change description" were used. It basically:
>
> 1. repeated the patch title,
> 2. spent one sentence only for mentioning a function name without giving
> any more information,
> 3. mentioned why some change was not necessary due to some other
> existing code, but not explicitly calling that part out, then
> 4. finished with a sentence that boiled down to "we should do the
> similar thing".
>
> My take:
>
> > Subject: Fix CMDLINE_EXTEND and CMDLINE_BOOTLOADER on non-FDT systems
> >
> > On FDT systems these command line processing are already taken care of
> > by early_init_dt_scan_chosen(). Add similar handling to the non-FDT
> > code path to allow these config options to work for non-FDT boxes too.
>
> Would this sound better?
>
Xuerui's take is fine. Do I need to make a v6 patch?
donmor
next prev parent reply other threads:[~2023-07-20 1:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 15:33 Huacai Chen
[not found] ` <261edc6c-e339-faeb-3045-bfe6604d1aef@web.de>
2023-07-19 7:22 ` Huacai Chen
2023-07-19 10:29 ` WANG Xuerui
2023-07-20 1:34 ` donmor [this message]
2023-07-20 1:39 ` Huacai Chen
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=281c5d5e51488ce51497072c1e4304d71af141ec.camel@hotmail.com \
--to=donmor3000@hotmail.com \
--cc=Markus.Elfring@web.de \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=guoren@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--cc=loongarch@lists.linux.dev \
--cc=loongson-kernel@lists.loongnix.cn \
/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®