From: Markus Elfring <Markus.Elfring@web.de>
To: Ricardo Ribalda <ribalda@chromium.org>,
Easwar Hariharan <eahariha@linux.microsoft.com>,
cocci@inria.fr
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Julia Lawall <Julia.Lawall@inria.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
Victor Gambier <victor.gambier@inria.fr>
Subject: Re: coccinelle: misc: secs_to_jiffies script: Create dummy report
Date: Wed, 29 Jan 2025 09:46:48 +0100 [thread overview]
Message-ID: <fce88885-8c10-4f22-a19c-3b04430aec3d@web.de> (raw)
In-Reply-To: <CANiDSCvufe0nK_NLykSRLb9RmttNOhw3-mm6aiC=gj41Hxtgiw@mail.gmail.com>
>>> 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?
>
> My main concern is to fix the CI that was broken when this semantic
> patch was introduced.
>
> I am sure that a person more capable on cocci patches can implement
> the report mode in a follow-up patch.
I prefer to avoid a temporary workaround when a more useful solution
is actually simple.
Regards,
Markus
next prev parent reply other threads:[~2025-01-29 8:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 8:06 [PATCH] " Ricardo Ribalda
2025-01-29 8:36 ` Markus Elfring
2025-01-29 8:40 ` Ricardo Ribalda
2025-01-29 8:46 ` Markus Elfring [this message]
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
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=fce88885-8c10-4f22-a19c-3b04430aec3d@web.de \
--to=markus.elfring@web.de \
--cc=Julia.Lawall@inria.fr \
--cc=akpm@linux-foundation.org \
--cc=cocci@inria.fr \
--cc=eahariha@linux.microsoft.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.palix@imag.fr \
--cc=ribalda@chromium.org \
--cc=victor.gambier@inria.fr \
/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
all inboxes | Powered by JetHome®