public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andy Whitcroft <apw@shadowen.org>, LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] checkpatch: Suggest pr_<level> over printk(KERN_<LEVEL>
Date: Mon, 12 Mar 2012 23:23:03 -0700	[thread overview]
Message-ID: <1331619783.7100.8.camel@joe2Laptop> (raw)
In-Reply-To: <1330667673.1939.22.camel@joe2Laptop>

Suggest the shorter pr_<level> instead of printk(KERN_<LEVEL>.

Prefer to use pr_<level> over bare printks.
Prefer to use pr_warn over pr_warning.

Signed-off-by: Joe Perches <joe@perches.com>
---
 scripts/checkpatch.pl |   13 +++++++++++++
 1 files changed, 13 insertions(+), 0 deletions(-)

diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 04eb9eb..ac2bbea 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -2379,6 +2379,19 @@ sub process {
 			}
 		}
 
+		if ($line =~ /\bprintk\s*\(\s*KERN_([A-Z]+)/) {
+			my $orig = $1;
+			my $level = lc($orig);
+			$level = "warn" if ($level eq "warning");
+			WARN("PREFER_PR_LEVEL",
+			     "Prefer pr_$level(... to printk(KERN_$1, ...\n" . $herecurr);
+		}
+
+		if ($line =~ /\bpr_warning\s*\(/) {
+			WARN("PREFER_PR_LEVEL",
+			     "Prefer pr_warn(... to pr_warning(...\n" . $herecurr);
+		}
+
 # function brace can't be on same line, except for #defines of do while,
 # or if closed on same line
 		if (($line=~/$Type\s*$Ident\(.*\).*\s{/) and



  reply	other threads:[~2012-03-13  6:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120302025554.GA13493@joana>
     [not found] ` <20120301.221643.881299898523907213.davem@davemloft.net>
     [not found]   ` <20120301.222316.1877216960521396397.davem@davemloft.net>
     [not found]     ` <20120301.222604.1508242694024394849.davem@davemloft.net>
     [not found]       ` <1330661602.1939.13.camel@joe2Laptop>
2012-03-02  5:35         ` [PATCH] checkpatch: Add --strict tests for braces, comments and casts Joe Perches
2012-03-02  5:54           ` [PATCH] checkpatch: Add --strict test for strings split across multiple lines Joe Perches
2012-03-13  6:23             ` Joe Perches [this message]
2012-03-13 12:05               ` [PATCH] checkpatch: Suggest pr_<level> over printk(KERN_<LEVEL> Ted Ts'o
2012-03-13 21:55                 ` Andrew Morton
2012-03-13 22:01                   ` Ted Ts'o
2012-03-13 22:03                     ` Andrew Morton
2012-03-14  0:31                       ` Ted Ts'o
2012-03-14  0:47                         ` Joe Perches
2012-03-14  1:07                           ` Ted Ts'o
2012-03-14  1:17                             ` Joe Perches
2012-03-14  2:19                               ` Ted Ts'o
2012-03-14  2:31                                 ` Joe Perches
2012-03-14  2:41                                   ` Ted Ts'o
2012-03-14  3:01                                     ` Joe Perches
2012-03-14 12:34                                       ` Ted Ts'o
2012-03-14 13:05                                         ` Joe Perches
2012-03-14 13:45                                           ` Ted Ts'o
2012-03-14 14:06                                             ` 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=1331619783.7100.8.camel@joe2Laptop \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@shadowen.org \
    --cc=linux-kernel@vger.kernel.org \
    /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