From: Joe Perches <joe@perches.com>
To: Ruslan Bilovol <ruslan.bilovol@gmail.com>,
apw@canonical.com, Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, keescook@chromium.org
Subject: Re: [PATCH RESEND] checkpatch: remove obsolete CONFIG_EXPERIMENTAL checks
Date: Mon, 27 Feb 2017 15:04:46 -0800 [thread overview]
Message-ID: <1488236686.25838.16.camel@perches.com> (raw)
In-Reply-To: <1488234097-20119-1-git-send-email-ruslan.bilovol@gmail.com>
On Tue, 2017-02-28 at 00:21 +0200, Ruslan Bilovol wrote:
> Config EXPERIMENTAL has been removed from kernel in 2013
> (see 3d374d0: "final removal of CONFIG_EXPERIMENTAL"),
> there is no any reason to do these checks now.
> Signed-off-by: Ruslan Bilovol <ruslan.bilovol@gmail.com>
While I think all the defconfigs that have CONFIG_EXPERIMENTAL
should have those lines removed, this seems sensible enough.
$ git grep -w CONFIG_EXPERIMENTAL -- "*defconfig*" | wc -l
216
Acked-by: Joe Perches <joe@perches.com>
Here's a little script to remove the CONFIG_EXPERIMENTAL
lines from all the defconfigs too:
$ git grep -w --name-only CONFIG_EXPERIMENTAL -- "*defconfig*" | \
xargs sed -i -e '/CONFIG_EXPERIMENTAL=[yn]/d'
> ---
> scripts/checkpatch.pl | 13 -------------
> 1 file changed, 13 deletions(-)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 982c52c..e0a34e6 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -2746,13 +2746,6 @@ sub process {
> #print "is_start<$is_start> is_end<$is_end> length<$length>\n";
> }
>
> -# discourage the addition of CONFIG_EXPERIMENTAL in Kconfig.
> - if ($realfile =~ /Kconfig/ &&
> - $line =~ /.\s*depends on\s+.*\bEXPERIMENTAL\b/) {
> - WARN("CONFIG_EXPERIMENTAL",
> - "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/) {
> @@ -3146,12 +3139,6 @@ sub process {
> }
> }
>
> -# discourage the addition of CONFIG_EXPERIMENTAL in #if(def).
> - if ($line =~ /^\+\s*\#\s*if.*\bCONFIG_EXPERIMENTAL\b/) {
> - WARN("CONFIG_EXPERIMENTAL",
> - "Use of CONFIG_EXPERIMENTAL is deprecated. For alternatives, see https://lkml.org/lkml/2012/10/23/580\n");
> - }
> -
> # check for RCS/CVS revision markers
> if ($rawline =~ /^\+.*\$(Revision|Log|Id)(?:\$|)/) {
> WARN("CVS_KEYWORD",
next prev parent reply other threads:[~2017-02-27 23:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 22:21 Ruslan Bilovol
2017-02-27 22:23 ` Kees Cook
2017-02-27 23:04 ` Joe Perches [this message]
2017-03-09 21:57 ` Ruslan Bilovol
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=1488236686.25838.16.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ruslan.bilovol@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®