From: Markus Elfring <Markus.Elfring@web.de>
To: Lyude Paul <lyude@redhat.com>
Cc: cocci@inria.fr
Subject: Re: [cocci] spatch really could use a --keep-going
Date: Mon, 4 Aug 2025 15:11:26 +0200 [thread overview]
Message-ID: <89dd6ea8-404e-4ce5-9d26-abd484fb69ff@web.de> (raw)
In-Reply-To: <4e009fd868cbb48aa802ce472715b5ffd7bcabac.camel@redhat.com>
> @depends on patch@
> @@
> (
> - local_irq_disable();
> + local_interrupt_disable();
> |
> - local_irq_enable();
> + local_interrupt_enable();
> )
I suggest to refine such an SmPL transformation approach like the following.
@replacements@
@@
(
-local_irq_disable
+local_interrupt_disable
|
-local_irq_enable
+local_interrupt_enable
)();
> Which brings me to ask: could we have a --keep-going option? The idea is very
> simple: don't stop performing transformations if coccinelle hits an error,
> simply either ignore and continue - or simply skip the one file that failed
> and continue. …
Has your fault tolerance any limits?
Regards,
Markus
prev parent reply other threads:[~2025-08-04 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 21:40 [cocci] spatch really could use a --keep-going Lyude Paul
2025-08-04 12:08 ` Julia Lawall
2025-08-04 13:11 ` Markus Elfring [this message]
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=89dd6ea8-404e-4ce5-9d26-abd484fb69ff@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=lyude@redhat.com \
/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