From: Yingjoe Chen <yingjoe.chen@mediatek.com>
To: Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>
Cc: <linux-kernel@vger.kernel.org>, Andi Kleen <ak@linux.intel.com>,
"Paul Bolle" <pebolle@tiscali.nl>, <srv_heupstream@mediatek.com>
Subject: Re: [PATCH v2 1/3] checkpatch: add Kconfig 'default n' test
Date: Wed, 4 May 2016 09:06:14 +0800 [thread overview]
Message-ID: <1462323974.4315.1.camel@mtksdaap41> (raw)
In-Reply-To: <1461335527-19270-1-git-send-email-yingjoe.chen@mediatek.com>
On Fri, 2016-04-22 at 22:32 +0800, Yingjoe Chen wrote:
> If a Kconfig config option doesn't specify 'default', the default
> will be n. Adding 'default n' is unnecessary.
>
> Add a test to warn about this.
>
> Signed-off-by: Yingjoe Chen <yingjoe.chen@mediatek.com>
> ---
> Change in v2:
> - Change according to Joe Perches' suggestion
>
> scripts/checkpatch.pl | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index d574d13..3cb7c2d 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -2600,6 +2600,13 @@ sub process {
> "Use of boolean is deprecated, please use bool instead.\n" . $herecurr);
> }
>
> +# discourage the use of default n
> + if ($realfile =~ /Kconfig/ &&
> + $line =~ /^\+\s*default\s*n\s*(#.*|$)/i) {
> + WARN("CONFIG_DEFAULT_N",
> + "Use of default n is unnecessary, default is n when omitted.\n" . $herecurr);
> + }
> +
> if (($realfile =~ /Makefile.*/ || $realfile =~ /Kbuild.*/) &&
> ($line =~ /\+(EXTRA_[A-Z]+FLAGS).*/)) {
> my $flag = $1;
Hi,
Any suggestion for this new round?
Joe.C
prev parent reply other threads:[~2016-05-04 1:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 14:32 [PATCH v2 1/3] checkpatch: add Kconfig 'default n' test Yingjoe Chen
2016-04-22 14:32 ` [PATCH v2 2/3] checkpatch: testing more config for Kconfig help text Yingjoe Chen
2016-04-22 14:32 ` [PATCH v2 3/3] checkpatch: relax Kconfig help text line number threshold Yingjoe Chen
2016-05-04 1:06 ` Yingjoe Chen [this message]
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=1462323974.4315.1.camel@mtksdaap41 \
--to=yingjoe.chen@mediatek.com \
--cc=ak@linux.intel.com \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=srv_heupstream@mediatek.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