From: Joe Perches <joe@perches.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Arvind Yadav <arvind.yadav.cs@gmail.com>,
rui.zhang@intel.com, edubezval@gmail.com
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] thermal/intel_powerclamp: pr_err()/pr_info() strings should end with newlines
Date: Mon, 09 Oct 2017 21:37:45 -0700 [thread overview]
Message-ID: <1507610265.3552.20.camel@perches.com> (raw)
In-Reply-To: <7555b065-f4de-2988-283b-b6800ce189ab@linaro.org>
On Mon, 2017-10-09 at 14:33 +0200, Daniel Lezcano wrote:
> On 09/10/2017 13:51, Arvind Yadav wrote:
> > pr_err()/pr_info() messages should end with a new-line to avoid
> > other messages being concatenated.
[]
> > diff --git a/drivers/thermal/intel_powerclamp.c b/drivers/thermal/intel_powerclamp.c
> > @@ -675,13 +675,13 @@ static int __init powerclamp_probe(void)
> > {
> >
> > if (!x86_match_cpu(intel_powerclamp_ids)) {
> > - pr_err("CPU does not support MWAIT");
> > + pr_err("CPU does not support MWAIT\n");
[etc...]
> Hi Arvind,
>
> you are sending these fixes for all the drivers around. There is a way
> to fix this once and for all: use the coccinelle tools [1], add the
> script in the changelog with a big patchset and add the script in the
> coccinelle scripts directory [2].
That can't work as any printk without a newline termination
could be followed by a printk(KERN_CONT/pr_cont( in another
function.
All of these must be hand-verified.
next prev parent reply other threads:[~2017-10-10 4:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 11:51 Arvind Yadav
2017-10-09 12:33 ` Daniel Lezcano
2017-10-10 4:37 ` Joe Perches [this message]
2017-10-10 8:24 ` Daniel Lezcano
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=1507610265.3552.20.camel@perches.com \
--to=joe@perches.com \
--cc=arvind.yadav.cs@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.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
Powered by JetHome