From: Joe Perches <joe@perches.com>
To: Nicolai Fischer <nicolai.fischer@fau.de>, linux-kernel@vger.kernel.org
Cc: apw@canonical.com, johannes.czekay@fau.de, linux-kernel@i4.cs.fau.de
Subject: Re: [PATCH 2/2] checkpatch: kconfig: add missing types to regex
Date: Sun, 20 Dec 2020 11:12:49 -0800 [thread overview]
Message-ID: <5e7eae6b12df8fefc900930ffc12f80a9bfd643c.camel@perches.com> (raw)
In-Reply-To: <a9797282-84c3-2c8f-73a0-d751a8201541@fau.de>
On Mon, 2020-12-14 at 11:24 +0100, Nicolai Fischer wrote:
> Kconfig parsing does not recognise all type attributes.
> This adds the missing 'int', 'sting' and 'hex' types.
>
> Signed-off-by: Nicolai Fischer <nicolai.fischer@fau.de>
> Co-developed-by: Johannes Czekay <johannes.czekay@fau.de>
> Signed-off-by: Johannes Czekay <johannes.czekay@fau.de>
[]
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -3321,7 +3321,7 @@ sub process {
> next if ($f =~ /^-/);
> last if (!$file && $f =~ /^\@\@/);
>
>
> - if ($lines[$ln - 1] =~ /^\+\s*(?:bool|tristate|prompt)\s*["']/) {
> + if ($lines[$ln - 1] =~ /^\+\s*(?:bool|tristate|int|hex|string|prompt)\s*["']/) {
int and hex uses are not required to be followed either a " or '
For that matter, it's not required for tristate, bool or string
Likely this should be ["'$]
$ git grep -P -oh '^\s*(?:bool|tristate|int|hex|string|prompt)\b\s*\S?' -- '*/Kconfig*' | \
sed -r -e 's/^\s+//' -e 's/\s+/ /g' | \
sort | uniq -c | sort -rn
8558 tristate "
6314 bool "
2082 bool
843 tristate
308 prompt "
286 int "
106 tristate '
93 int
84 hex "
66 string "
25 hex
21 bool '
18 string
5 hex '
3 string p
2 string (
1 string '
1 int.
1 bool #
1 bool
next prev parent reply other threads:[~2020-12-20 19:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 10:24 Nicolai Fischer
2020-12-20 19:12 ` Joe Perches [this message]
2020-12-20 19:16 ` Joe Perches
2020-12-21 15:08 ` Nicolai Fischer
2020-12-21 17:17 ` Joe Perches
2020-12-25 17:27 ` Nicolai Fischer
2020-12-25 17:42 ` 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=5e7eae6b12df8fefc900930ffc12f80a9bfd643c.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=johannes.czekay@fau.de \
--cc=linux-kernel@i4.cs.fau.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolai.fischer@fau.de \
/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®