From: Joe Perches <joe@perches.com>
To: Levente Kurusa <levex@linux.com>
Cc: Yogesh Chaudhari <mr.yogesh@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
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 07:40:26 -0800 [thread overview]
Message-ID: <1393774826.13719.31.camel@joe-AO722> (raw)
In-Reply-To: <53134C4D.2090406@linux.com>
On Sun, 2014-03-02 at 16:20 +0100, Levente Kurusa wrote:
> 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.
maybe:
"Prefer [subsystem eg: netdev]_$level2 then dev_$level2 then pr_$level to printk(KERN_$orig ...\n"
or reference the stackoverflow link
next prev parent reply other threads:[~2014-03-02 15:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-02 15:01 Yogesh Chaudhari
2014-03-02 15:14 ` Joe Perches
2014-03-02 15:20 ` Levente Kurusa
[not found] ` <CAAOfnZqjVn5_aTU3fQQmOF8MqOb5NqXS5Yg4gb-Sec+Qm_0dEQ@mail.gmail.com>
2014-03-02 15:34 ` Levente Kurusa
2014-03-02 15:40 ` Joe Perches [this message]
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=1393774826.13719.31.camel@joe-AO722 \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=levex@linux.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
all inboxes | Powered by JetHome®