From: Maninder Singh <maninder1.s@samsung.com>
To: apw@canonical.com, joe@perches.com, dwaipayanray1@gmail.com,
lukas.bulwahn@gmail.com
Cc: linux-kernel@vger.kernel.org, a.sahrawat@samsung.com,
Maninder Singh <maninder1.s@samsung.com>,
Vaneet Narang <v.narang@samsung.com>
Subject: [PATCH 1/1] scripts/checkpatch.pl: remove warning for pritk_deferred also
Date: Tue, 24 Aug 2021 12:05:00 +0530 [thread overview]
Message-ID: <1629786900-4644-1-git-send-email-maninder1.s@samsung.com> (raw)
In-Reply-To: <CGME20210824063513epcas5p46ba8b375c3e32fab210640a28041efb6@epcas5p4.samsung.com>
printk_deferred also supossed to get loglevel, but checkpatch.pl
returns warning for same.
WARNING: Possible unnecessary KERN_ALERT
+printk_deferred(KERN_ALERT "checking deferred\n");
total: 0 errors, 1 warnings, 20 lines checked
Thus removing warning for printk_deferred also.
Signed-off-by: Vaneet Narang <v.narang@samsung.com>
Signed-off-by: Maninder Singh <maninder1.s@samsung.com>
---
scripts/checkpatch.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 161ce7fe5d1e..e3bea0d36c10 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -6252,7 +6252,7 @@ sub process {
}
# check for logging functions with KERN_<LEVEL>
- if ($line !~ /printk(?:_ratelimited|_once)?\s*\(/ &&
+ if ($line !~ /printk(?:_ratelimited|_once|_deferred)?\s*\(/ &&
$line =~ /\b$logFunctions\s*\(.*\b(KERN_[A-Z]+)\b/) {
my $level = $1;
if (WARN("UNNECESSARY_KERN_LEVEL",
--
2.17.1
next parent reply other threads:[~2021-08-24 7:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210824063513epcas5p46ba8b375c3e32fab210640a28041efb6@epcas5p4.samsung.com>
2021-08-24 6:35 ` Maninder Singh [this message]
[not found] ` <CGME20210824063513epcas5p46ba8b375c3e32fab210640a28041efb6@epcms5p8>
2021-09-06 12:41 ` Maninder Singh
2021-09-06 20:15 ` Andy Whitcroft
[not found] ` <CGME20210824063513epcas5p46ba8b375c3e32fab210640a28041efb6@epcms5p3>
2021-09-10 12:45 ` Maninder Singh
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=1629786900-4644-1-git-send-email-maninder1.s@samsung.com \
--to=maninder1.s@samsung.com \
--cc=a.sahrawat@samsung.com \
--cc=apw@canonical.com \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=v.narang@samsung.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®