From: Joe Perches <joe@perches.com>
To: Philipp Hahn <phahn-oss@avm.de>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Cc: Andy Whitcroft <apw@canonical.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Philipp Hahn <p.hahn@avm.de>
Subject: Re: [PATCH] checkpatch: Describe --min-conf-desc-length
Date: Mon, 10 Mar 2025 12:38:22 -0700 [thread overview]
Message-ID: <95d462018382f51ac88471fb555653b2b6601100.camel@perches.com> (raw)
In-Reply-To: <c71c170c90eba26265951e248adfedd3245fe575.1741605695.git.p.hahn@avm.de>
On Mon, 2025-03-10 at 12:22 +0100, Philipp Hahn wrote:
> Neither the warning nor the help message gives any hint on the unit for
> length: Could be meters, inches, bytes, characters or ... lines.
I've no objection to this.
>
> Extend the output of `--help` to name the unit "lines" and the default:
> - --min-conf-desc-length=n set the min description length, if shorter, warn
> + --min-conf-desc-length=n set the minimum description length for config symbols
> + in lines, if shorter, warn (default 4)
>
> Include the minimum number of lines as other error messages already do:
> - WARNING: please write a help paragraph that fully describes the config symbol
> + WARNING: please write a help paragraph that fully describes the config symbol with at least 4 lines
>
> Cc: Andy Whitcroft <apw@canonical.com>
> Cc: Joe Perches <joe@perches.com>
> Cc: Dwaipayan Ray <dwaipayanray1@gmail.com>
> Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> Signed-off-by: Philipp Hahn <p.hahn@avm.de>
> ---
> scripts/checkpatch.pl | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 7b28ad331742..784912f570e9 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -113,7 +113,8 @@ Options:
> --max-line-length=n set the maximum line length, (default $max_line_length)
> if exceeded, warn on patches
> requires --strict for use with --file
> - --min-conf-desc-length=n set the min description length, if shorter, warn
> + --min-conf-desc-length=n set the minimum description length for config symbols
> + in lines, if shorter, warn (default $min_conf_desc_length)
> --tab-size=n set the number of spaces for tab (default $tabsize)
> --root=PATH PATH to the kernel tree root
> --no-summary suppress the per-file summary
> @@ -3645,7 +3646,7 @@ sub process {
> $help_length < $min_conf_desc_length) {
> my $stat_real = get_stat_real($linenr, $ln - 1);
> WARN("CONFIG_DESCRIPTION",
> - "please write a help paragraph that fully describes the config symbol\n" . "$here\n$stat_real\n");
> + "please write a help paragraph that fully describes the config symbol with at least $min_conf_desc_length lines\n" . "$here\n$stat_real\n");
> }
> }
>
prev parent reply other threads:[~2025-03-10 19:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 11:22 Philipp Hahn
2025-03-10 19:38 ` Joe Perches [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=95d462018382f51ac88471fb555653b2b6601100.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=dwaipayanray1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=p.hahn@avm.de \
--cc=phahn-oss@avm.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®