[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <af04860002d4b0f4607bd4ce6d767f5705430ace.camel@perches.com>
Date: Wed, 19 Dec 2018 02:44:36 -0800
From: Joe Perches <joe@...ches.com>
To: Igor Stoppa <igor.stoppa@...il.com>,
Andy Whitcroft <apw@...onical.com>
Cc: igor.stoppa@...wei.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] checkpatch.pl: Improve WARNING on Kconfig help
On Wed, 2018-12-19 at 10:35 +0200, Igor Stoppa wrote:
> The checkpatch.pl script complains when the help section of a Kconfig
> entry is too short, but it doesn't really explain what it is looking
> for. Instead, it gives a generic warning that one should consider writing
> a paragraph.
>
> But what it *really* checks is that the help section is at least
> .$min_conf_desc_length lines long.
>
> Since the definition of what is a paragraph is not really carved in
> stone (and actually the primary descriptions is "5 sentences"), make the
> warning less ambiguous by expliciting the actual test condition, so that
> one doesn't have to read checkpatch.pl sources, to figure out the actual
> test.
[]
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -2931,7 +2931,8 @@ sub process {
> }
> if ($is_start && $is_end && $length < $min_conf_desc_length) {
> WARN("CONFIG_DESCRIPTION",
> - "please write a paragraph that describes the config symbol fully\n" . $herecurr);
> + "please write a paragraph (" .$min_conf_desc_length . " lines)" .
could say "(at least $min_conf_desc_length lines)"
Powered by blists - more mailing lists