>> - add "path/to/file.c" when using Coccinelle to check a single file
…
> Acked-by: Julia Lawall
Do you really acknowledge that the specified make command is working
in the expected way?
Would you like to mention any source file then for which known
source code analysis (or transformation) resu
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 us
>> …
>>> +++ 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/cocc
On 6/30/20 5:23 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::
>>
>> -
…
> +++ 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
> @@ -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
Can such information
6 matches
Mail list logo