lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 2 Jul 2020 10:22:27 +0200 From: Markus Elfring <Markus.Elfring@....de> To: Julia Lawall <julia.lawall@...ia.fr>, Randy Dunlap <rdunlap@...radead.org>, Coccinelle <cocci@...teme.lip6.fr>, linux-doc@...r.kernel.org Cc: kernel-janitors@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>, Jonathan Corbet <corbet@....net>, Masahiro Yamada <masahiroy@...nel.org>, Michal Marek <michal.lkml@...kovi.net>, Nicolas Palix <nicolas.palix@...g.fr>, Gilles Muller <Gilles.Muller@...6.fr> Subject: Re: [v2] Documentation: Coccinelle: fix typos and command example >> elfring@...ne:~/Projekte/Linux/next-patched> make J=1 C=1 CHECK='scripts/coccicheck' MODE=context COCCI=~/Projekte/Linux/next-patched/scripts/coccinelle/null/show_pointer_usage_before_null_check-20200701.cocci drivers/usb/mtu3/mtu3_gadget.o > > This is not what is intended. What is intended has never worked. The > coccicheck script expects that the file name is received on its command > line, and that is not the case. I suggest to take another look at information from the verbose execution variant for such a command example. * Do the generated program calls look more appropriate then? * Are you still missing any relevant data (or corresponding descriptions)? Regards, Markus
Powered by blists - more mailing lists