From: Paul Bolle <pebolle@tiscali.nl>
To: Christoph Jaeger <cj@linux.com>
Cc: apw@canonical.com, joe@perches.com, linux-kernel@vger.kernel.org,
dborkman@redhat.com
Subject: Re: [PATCH] checkpatch: add check for keyword 'boolean' in Kconfig definitions
Date: Tue, 06 Jan 2015 00:16:16 +0100 [thread overview]
Message-ID: <1420499776.14308.50.camel@x220> (raw)
In-Reply-To: <1419108036-11536-1-git-send-email-cj@linux.com>
On Sat, 2014-12-20 at 15:40 -0500, Christoph Jaeger wrote:
> Discourage the use of keyword 'boolean' for type definition attributes of
> config options as support for it will be dropped later on.
>
> Reference: http://lkml.kernel.org/r/cover.1418003065.git.cj@linux.com
> Suggested-by: Daniel Borkmann <dborkman@redhat.com>
> Signed-off-by: Christoph Jaeger <cj@linux.com>
Works as advertised:
$ scripts/checkpatch.pl -f kernel/livepatch/Kconfig
WARNING: Use of boolean is deprecated, please use bool instead.
#2: FILE: kernel/livepatch/Kconfig:2:
+ boolean
WARNING: Use of boolean is deprecated, please use bool instead.
#7: FILE: kernel/livepatch/Kconfig:7:
+ boolean "Kernel Live Patching"
total: 0 errors, 2 warnings, 18 lines checked
kernel/livepatch/Kconfig has style problems, please review.
If any of these errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
Acked-by: Paul Bolle <pebolle@tiscali.nl>
> ---
> scripts/checkpatch.pl | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index f0bb6d6..cae974e 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -2355,6 +2355,13 @@ sub process {
> "Use of CONFIG_EXPERIMENTAL is deprecated. For alternatives, see https://lkml.org/lkml/2012/10/23/580\n");
> }
>
> +# discourage the use of boolean for type definition attributes of Kconfig options
> + if ($realfile =~ /Kconfig/ &&
> + $line =~ /^\+\s*\bboolean\b/) {
> + WARN("CONFIG_TYPE_BOOLEAN",
This should become an error once "boolean" is removed (on some future
date).
> + "Use of boolean is deprecated, please use bool instead.\n" . $herecurr);
> + }
> +
> if (($realfile =~ /Makefile.*/ || $realfile =~ /Kbuild.*/) &&
> ($line =~ /\+(EXTRA_[A-Z]+FLAGS).*/)) {
> my $flag = $1;
Paul Bolle
prev parent reply other threads:[~2015-01-05 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 20:40 Christoph Jaeger
2014-12-20 20:49 ` Joe Perches
2015-01-05 23:16 ` Paul Bolle [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=1420499776.14308.50.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=apw@canonical.com \
--cc=cj@linux.com \
--cc=dborkman@redhat.com \
--cc=joe@perches.com \
--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
Powered by JetHome