[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <05f8cb2b-c76e-e2ba-24a8-5676c1792255@infradead.org>
Date: Wed, 1 Jul 2020 12:15:13 -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 <masahiroy@...nel.org>,
Jonathan Corbet <corbet@....net>
Subject: Re: [v2] Documentation: Coccinelle: fix typos and command example
On 7/1/20 10:32 AM, Markus Elfring wrote:
>> None of that has anything to do with the current patch.
>
> Did you test the specified make command for the display
> of expected data processing results?
Markus, if something doesn't work, just say so, OK?
Don't go all obtuse on us.
> How much do you distinguish desired effects according to
> the specification of file extensions for such build commands?
I don't grok that.
@Jon, Julia-
I plan to submit a v3 without the addition of "path/to/file.c" in 2 places.
However, I thought that this:
To apply Coccinelle on a file basis, instead of a directory basis, the
following command may be used::
make C=1 CHECK="scripts/coccicheck"
meant that someone could run coccicheck on one source file, but I cannot
get that to work.
Julia, Markus- can you tell me how to run coccicheck on one source file?
Thanks.
--
~Randy
Powered by blists - more mailing lists