From: Julia Lawall <julia.lawall@inria.fr>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>, cocci@inria.fr
Subject: Re: [cocci] Transforming data structure accesses with SmPL
Date: Thu, 21 Dec 2023 13:57:28 +0100 (CET) [thread overview]
Message-ID: <6253ddc-2c97-aaa2-63a2-4181f4703460@inria.fr> (raw)
In-Reply-To: <fe67dbb7-7dc9-40a4-a136-19a659e35fd6@web.de>
On Thu, 21 Dec 2023, Markus Elfring wrote:
> > In general, I don't want to spend my time on perfecting a .cocci script as
> > further improvements tend to be needed around the areas highlighted
> > anyway. It's enough for me that the most mechanical transformation cases
> > are covered by spatch and I can handle the troublemakers myself while
> > inspecting the results.
Seems fine to me :)
julia
prev parent reply other threads:[~2023-12-21 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 8:44 [cocci] Spatch corrupting struct variable Ilpo Järvinen
2023-12-21 9:01 ` Julia Lawall
2023-12-21 9:44 ` Ilpo Järvinen
2023-12-21 11:16 ` [cocci] Transforming data structure accesses with SmPL Markus Elfring
[not found] ` <80d307c-e3f7-8f84-78d4-b19113f441f7@linux.intel.com>
2023-12-21 12:52 ` Markus Elfring
2023-12-21 12:57 ` Julia Lawall [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=6253ddc-2c97-aaa2-63a2-4181f4703460@inria.fr \
--to=julia.lawall@inria.fr \
--cc=Markus.Elfring@web.de \
--cc=cocci@inria.fr \
--cc=ilpo.jarvinen@linux.intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).