From: Joe Perches <joe@perches.com>
To: Al Viro <viro@zeniv.linux.org.uk>, zhouchuangao <chuangaozhou@gmail.com>
Cc: linux@dominikbrodowski.net, pc@cjr.nz, axboe@kernel.dk,
dhowells@redhat.com, linux-kernel@vger.kernel.org,
zhouchuangao <zhouchuangao@xiaomi.com>
Subject: Re: [PATCH] init/do_mounts: fix a coding style error
Date: Sun, 26 Jul 2020 10:50:55 -0700 [thread overview]
Message-ID: <fc092be37e970b0ec474e46e31c13ba1e1fae675.camel@perches.com> (raw)
In-Reply-To: <20200726172109.GV2786714@ZenIV.linux.org.uk>
On Sun, 2020-07-26 at 18:21 +0100, Al Viro wrote:
> On Tue, Jul 14, 2020 at 03:02:58PM +0800, zhouchuangao wrote:
> > Fix code style errors reported by scripts/checkpatch.pl.
>
> NAKed-because: excessive deference to checkpatch.pl
>
> It's not a holy oracle than needs to be appeased, no questions
> asked. Reference to it is absolutely insufficient reason for
> _anything_ - in effect your commit message could've been
> "just because" for all the information it contains.
Al is right.
Something that could useful is to avoid using printks without
a KERN_<LEVEL> or add KERN_CONT to some continuation printks.
Maybe:
---
diff --git a/init/do_mounts.c b/init/do_mounts.c
index 4f4ceb358055..3f37d859cf2a 100644
--- a/init/do_mounts.c
+++ b/init/do_mounts.c
@@ -468,8 +468,8 @@ void __init mount_block_root(char *name, int flags)
printk_all_partitions();
printk("No filesystem could mount root, tried: ");
for (p = fs_names; *p; p += strlen(p)+1)
- printk(" %s", p);
- printk("\n");
+ pr_cont(" %s", p);
+ pr_cont("\n");
panic("VFS: Unable to mount root fs on %s", b);
out:
put_page(page);
next prev parent reply other threads:[~2020-07-26 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 7:02 zhouchuangao
2020-07-26 17:21 ` Al Viro
2020-07-26 17:50 ` Joe Perches [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-21 3:41 zhouchuangao
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=fc092be37e970b0ec474e46e31c13ba1e1fae675.camel@perches.com \
--to=joe@perches.com \
--cc=axboe@kernel.dk \
--cc=chuangaozhou@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=pc@cjr.nz \
--cc=viro@zeniv.linux.org.uk \
--cc=zhouchuangao@xiaomi.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
all inboxes | Powered by JetHome®