public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@linaro.org>
To: Joe Perches <joe@perches.com>
Cc: Andy Whitcroft <apw@canonical.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] checkpatch: Fix checks for Kconfig help text
Date: Sat, 18 Nov 2017 16:46:11 +0800	[thread overview]
Message-ID: <20171118084611.GA9096@leoy-linaro> (raw)
In-Reply-To: <1510321347.15768.79.camel@perches.com>

On Fri, Nov 10, 2017 at 05:42:27AM -0800, Joe Perches wrote:
> On Fri, 2017-11-10 at 14:42 +0800, Leo Yan wrote:
> > If one patch has Kconfig section, the check script variable '$is_start'
> > will be set by first 'config' line and the variable '$is_end' is to be
> > set by the second 'config' line. But patches often only has one
> > 'config' line so we have no chance to set '$is_end', as result below
> > condition is invalid and it skips check for Kconfig description:
> > 
> > 	if ($is_start && $is_end && $length < $min_conf_desc_length) {
> > 		......
> > 	}
> > 
> > When script runs to this condition sentence it means the Kconfig
> > section parsing has been completed, whatever '$is_end' is true
> > or not. So removes '$is_end' from condition sentence.
> > 
> > Another change is to change '$min_conf_desc_length' from 4 to 1; so can
> > pass the check if Kconfig description has at least one line.
> 
> Hello Leo.
> 
> I do not like this.
> 
> Separate changes please and that $min_conf_desc_length
> change is definitely not a fix.  It's a preference.

Thank you for suggestion, Joe. Will send new patches soon.

Thanks,
Leo Yan

> > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> []
> > @@ -51,7 +51,7 @@ my $configuration_file = ".checkpatch.conf";
> >  my $max_line_length = 80;
> >  my $ignore_perl_version = 0;
> >  my $minimum_perl_version = 5.10.0;
> > -my $min_conf_desc_length = 4;
> > +my $min_conf_desc_length = 1;
> >  my $spelling_file = "$D/spelling.txt";
> >  my $codespell = 0;
> >  my $codespellfile = "/usr/share/codespell/dictionary.txt";
> > @@ -2796,7 +2796,7 @@ sub process {
> >  				}
> >  				$length++;
> >  			}
> > -			if ($is_start && $is_end && $length < $min_conf_desc_length) {
> > +			if ($is_start && $length < $min_conf_desc_length) {
> >  				WARN("CONFIG_DESCRIPTION",
> >  				     "please write a paragraph that describes the config symbol fully\n" . $herecurr);
> >  			}

      reply	other threads:[~2017-11-18  8:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-10  6:42 [PATCH v2] checkpatch: Fix checks for Kconfig help text Leo Yan
2017-11-10 13:42 ` Joe Perches
2017-11-18  8:46   ` Leo Yan [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=20171118084611.GA9096@leoy-linaro \
    --to=leo.yan@linaro.org \
    --cc=apw@canonical.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