[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fe13604a-2626-4641-908e-87eeaca53288@web.de>
Date: Wed, 29 Jan 2025 09:36:29 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Ricardo Ribalda <ribalda@...omium.org>,
Easwar Hariharan <eahariha@...ux.microsoft.com>, cocci@...ia.fr
Cc: LKML <linux-kernel@...r.kernel.org>, kernel-janitors@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Julia Lawall <Julia.Lawall@...ia.fr>, Nicolas Palix <nicolas.palix@...g.fr>,
Victor Gambier <victor.gambier@...ia.fr>
Subject: Re: [PATCH] coccinelle: misc: secs_to_jiffies script: Create dummy
report
> When running cocci in report mode, eg:
> $make coccicheck M="$dir" MODE=report
>
> It returns this error:
> virtual rule report not supported
> coccicheck failed
> make: *** [Makefile:251: __sub-make] Error 2
I hope that more collateral evolution will happen because of such information.
> Create a dummy rule to avoid this error and run the other cocci scripts.
Please add proper support for operation modes around discussed source code analysis approaches.
Will it be more helpful to work with function calls like the following?
‣ coccilib.org.print_todo(p[0], "WARNING: opportunity for …")
‣ coccilib.report.print_report(p[0], "WARNING: opportunity for …")
Regards,
Markus
Powered by blists - more mailing lists