[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f2aaa91a-f935-bc2d-26f2-712576c1bbd7@infradead.org>
Date: Wed, 1 Jul 2020 06:20:34 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Markus Elfring <Markus.Elfring@....de>, linux-doc@...r.kernel.org,
Coccinelle <cocci@...teme.lip6.fr>
Cc: LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org,
Julia Lawall <julia.lawall@...6.fr>,
Gilles Muller <Gilles.Muller@...6.fr>,
Nicolas Palix <nicolas.palix@...g.fr>,
Michal Marek <michal.lkml@...kovi.net>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH v2] Documentation: Coccinelle: fix typos and command
example
On 7/1/20 4:56 AM, Markus Elfring wrote:
>>> …
>>>> +++ linux-next-20200629/Documentation/dev-tools/coccinelle.rst
>>> …
>>>> @@ -177,13 +177,13 @@ For example, to check drivers/net/wirele
>>>> To apply Coccinelle on a file basis, instead of a directory basis, the
>>>> following command may be used::
>>>>
>>>> - make C=1 CHECK="scripts/coccicheck"
>>>> + make C=1 CHECK="scripts/coccicheck" path/to/file.c
> …
>>> We might stumble on different interpretations according to the wording “file basis”.
>>> Do you find a message like “make: Nothing to be done for 'path/to/file.c'.” interesting then?
>>>
>>> * Would you like to add any links for information around the support for
>>> source code checkers?
>>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Makefile?id=7c30b859a947535f2213277e827d7ac7dcff9c84#n198
> …
>> Feel free to submit patches.
>
> How do you think about to use the following command variant
> for the adjustment of the software documentation?
>
> + make C=1 CHECK='scripts/coccicheck' 'path/to/file.o'
>
I don't understand the reason for that change...
--
~Randy
Powered by blists - more mailing lists