From: Easwar Hariharan <eahariha@linux.microsoft.com>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: eahariha@linux.microsoft.com,
Julia Lawall <Julia.Lawall@inria.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
Andrew Morton <akpm@linux-foundation.org>,
cocci@inria.fr, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] coccinelle: misc: secs_to_jiffies script: Create dummy report
Date: Tue, 10 Jun 2025 10:35:52 -0700 [thread overview]
Message-ID: <588d5a4b-72cf-4d2c-8eee-c4240ae067b5@linux.microsoft.com> (raw)
In-Reply-To: <CANiDSCviy5SjOwEcEM8_1gtvQzFUS3d=S6vFdvZzVqbif7NKfA@mail.gmail.com>
On 6/10/2025 6:09 AM, Ricardo Ribalda wrote:
> Hi
>
> On Wed, 29 Jan 2025 at 18:38, Easwar Hariharan
> <eahariha@linux.microsoft.com> wrote:
>>
>> On 1/29/2025 12:06 AM, Ricardo Ribalda wrote:
>>> 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
>>>
>>> Create a dummy rule to avoid this error and run the other cocci scripts.
>>>
>>> Fixes: 551dbd1ec7ff ("coccinelle: misc: add secs_to_jiffies script")
>>> Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
>>> ---
>>> scripts/coccinelle/misc/secs_to_jiffies.cocci | 6 ++++++
>>> 1 file changed, 6 insertions(+)
>>>
>>> diff --git a/scripts/coccinelle/misc/secs_to_jiffies.cocci b/scripts/coccinelle/misc/secs_to_jiffies.cocci
>>> index 8bbb2884ea5d..2d85dca16418 100644
>>> --- a/scripts/coccinelle/misc/secs_to_jiffies.cocci
>>> +++ b/scripts/coccinelle/misc/secs_to_jiffies.cocci
>>> @@ -10,6 +10,7 @@
>>> //
>>>
>>> virtual patch
>>> +virtual report
>>>
>>> @depends on patch@ constant C; @@
>>>
>>> @@ -20,3 +21,8 @@ virtual patch
>>>
>>> - msecs_to_jiffies(C * MSEC_PER_SEC)
>>> + secs_to_jiffies(C)
>>> +
>>> +// Dummy rule for report mode that would otherwise be empty and make spatch
>>> +// fail ("No rules apply.")
>>> +@script:python depends on report@
>>> +@@
>>>
>>
>> Sorry about that, and thanks for the patch!
>>
>> FWIW,
>>
>> Reviewed-by: Easwar Hariharan <eahariha@linux.microsoft.com>
>
> I just checked on 6.16rc1 and it is still failing.
>
> Could we land this while Mark's series is under review?
>
> Thanks!
>
Can you provide a pointer to Mark's series? I actually just implemented a proper report and context mode
which I'm glad to send out.
Thanks,
Easwar (he/him)
next prev parent reply other threads:[~2025-06-10 17:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 8:06 Ricardo Ribalda
2025-01-29 8:36 ` Markus Elfring
2025-01-29 8:40 ` Ricardo Ribalda
2025-01-29 8:46 ` Markus Elfring
2025-01-29 9:51 ` Victor Gambier
2025-01-29 9:56 ` Markus Elfring
2025-01-31 10:05 ` Markus Elfring
2025-01-29 17:38 ` [PATCH] " Easwar Hariharan
2025-06-10 13:09 ` Ricardo Ribalda
2025-06-10 17:35 ` Easwar Hariharan [this message]
2025-06-11 7:59 ` Ricardo Ribalda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=588d5a4b-72cf-4d2c-8eee-c4240ae067b5@linux.microsoft.com \
--to=eahariha@linux.microsoft.com \
--cc=Julia.Lawall@inria.fr \
--cc=akpm@linux-foundation.org \
--cc=cocci@inria.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.palix@imag.fr \
--cc=ribalda@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome