From: Levente Kurusa <levex@linux.com>
To: Yogesh Chaudhari <mr.yogesh@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Cc: joe@perches.com, apw@canonical.com
Subject: Re: [PATCH 1/1] scripts/checkpatch.pl: to give more detailed warning message in case printk is used in any patch
Date: Sun, 02 Mar 2014 16:20:45 +0100 [thread overview]
Message-ID: <53134C4D.2090406@linux.com> (raw)
In-Reply-To: <CAAOfnZp-KAFo8Q4bBW7oxe8BgUn+bSDAWuHbK6E+SF0X0Ex=Wg@mail.gmail.com>
Hi,
On 03/02/2014 04:01 PM, Yogesh Chaudhari wrote:
> Based on the discussion here:
> https://lkml.org/lkml/2014/3/2/17
>
> I would like to propose this patch to improve the warning message in
> checkpatch.pl. Comments/Suggestions on possible improvements are
> welcome.
>
>
> =========================================================
>
> This patch modifies scripts/checkpatch.pl to give more detailed
> warning message in case printk is used in any patch.
>
> Signed-off-by: Yogesh Chaudhari <mr.yogesh@gmail.com>
> ---
> scripts/checkpatch.pl | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 464dcef..526f33aa 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -2799,7 +2799,10 @@ sub process {
> my $level2 = $level;
> $level2 = "dbg" if ($level eq "debug");
> WARN("PREFER_PR_LEVEL",
> - "Prefer netdev_$level2(netdev, ... then
> dev_$level2(dev, ... then pr_$level(... to printk(KERN_$orig ...\n" .
> $herecurr);
Whoops, that's a word-wrap!
Try using git-format-patch+git-send-email to send the patch.
> + "Order of preference for printing debug messages:
> + 1. [subsystem]_$level2([subsystem]dev, ... eg
> netdev_$level2(netdev, ... for netdevice object
> + 2. dev_$level2(dev, ... for drivers with struct device
> + 3. pr_$level(... to printk(KERN_$orig ...\n" . $herecurr);
> }
>
> if ($line =~ /\bpr_warning\s*\(/) {
>
IMHO, this message is too big. The one we already have is nice and clean.
I would simply do: s/netdev/[subsystem]/ or something among the lines.
--
Regards,
Levente Kurusa
next prev parent reply other threads:[~2014-03-02 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-02 15:01 [PATCH 1/1] scripts/checkpatch.pl: to give more detailed warning message in case printk is used in any patch Yogesh Chaudhari
2014-03-02 15:14 ` Joe Perches
2014-03-02 15:20 ` Levente Kurusa [this message]
[not found] ` <CAAOfnZqjVn5_aTU3fQQmOF8MqOb5NqXS5Yg4gb-Sec+Qm_0dEQ@mail.gmail.com>
2014-03-02 15:34 ` Levente Kurusa
2014-03-02 15:40 ` Joe Perches
2014-03-02 15:49 ` Levente Kurusa
2014-03-02 16:21 ` Yogesh Chaudhari
2014-03-02 18:54 ` Joe Perches
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=53134C4D.2090406@linux.com \
--to=levex@linux.com \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mr.yogesh@gmail.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