[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fa4e75fa79a89b20f903364acc604cf0796b5421.camel@perches.com>
Date: Wed, 02 Dec 2020 11:14:49 -0800
From: Joe Perches <joe@...ches.com>
To: Randy Dunlap <rdunlap@...radead.org>,
Nicolai Fischer <nicolai.fischer@....de>,
linux-kernel@...r.kernel.org, Andi Kleen <ak@...ux.intel.com>
Cc: apw@...onical.com, johannes.czekay@....de,
linux-kernel@...cs.fau.de
Subject: Re: [RFC PATCH] checkpatch: correctly detect lines of help text
On Wed, 2020-12-02 at 10:59 -0800, Randy Dunlap wrote:
> On 12/2/20 10:54 AM, Joe Perches wrote:
[]
> > Indentation can vary in the help blocks. For instance:
> >
> > arch/Kconfig: help
> > arch/Kconfig- Functions will have the stack-protector canary logic added in>
> > arch/Kconfig- of the following conditions:
> > arch/Kconfig-
> > arch/Kconfig- - local variable's address used as part of the right hand sid>
> > arch/Kconfig- assignment or function argument
> > arch/Kconfig- - local variable is an array (or union containing an array),
> > arch/Kconfig- regardless of array type or length
> > arch/Kconfig- - uses register local variables
> > arch/Kconfig-
> >
> > This doesn't allow blank lines for multi-paragraph help text either.
> >
> > I think keyword parsing is necessary and some false positives are
> > inevitable as the parsing logic in a line-by-line analyzer will
> > always be incomplete.
>
> There are also large hunks of block/Kconfig and drivers/hid/Kconfig
> that don't use any indentation for help text...
> in case that matters here.
Maybe a wholesale conversion of Kconfig help text could be done moving
any help block not already as the last entry to be the last entry and
indenting any paragraph help text not already indented 2 extra spaces.
Should be reasonably scriptable given the parser logic available in
scripts/kconfig/.
Something akin to the scripts/parse-maintainers.pl script.
Powered by blists - more mailing lists