From: Markus Elfring <Markus.Elfring@web.de>
To: "Jérémy Lefaure" <jeremy.lefaure@netatmo.com>,
cocci@inria.fr, kernel-janitors@vger.kernel.org
Cc: Nicolas Palix <nicolas.palix@imag.fr>,
Julia Lawall <julia.lawall@inria.fr>
Subject: Re: [cocci] [PATCH v5] coccinelle: Extend address test from ifaddr semantic patch to test expressions
Date: Sun, 3 Jul 2022 13:34:40 +0200 [thread overview]
Message-ID: <8ec4c66d-a315-5c64-7f7f-f707a175d56c@web.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2207021218550.2882@hadrien>
> If you want a feature to be added, ask for the feature.
> But please stop confusing the discussion about semantic patches
> that are proposed by other people.
Would you like to achieve that all basic coccicheck operation modes will become
properly supported for a SmPL code variant like the following?
@display@
type t;
statement is, es;
identifier i;
expression x, ix, ex, z;
binary operator bo;
@@
(
*if (&(x))
is
else
es
|
* &(x) bo NULL
|
* NULL bo &(x)
|
* !(&(x))
|
* (&(x))
? (ix)
: (ex)
|
t i =
* (&(x))
;
|
(z =
* &(x)
)
)
Regards,
Markus
next prev parent reply other threads:[~2022-07-03 11:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 16:01 [cocci] [PATCH v5] coccinelle: Extend address test from ifaddr semantic patch to test expressions Jérémy LEFAURE
2022-07-01 16:55 ` Markus Elfring
2022-07-01 19:30 ` Markus Elfring
2022-07-01 20:49 ` Julia Lawall
2022-07-01 21:13 ` [cocci] [v5] " Markus Elfring
2022-07-02 8:01 ` [cocci] [PATCH v5] " Markus Elfring
2022-07-02 10:21 ` Julia Lawall
2022-07-02 11:00 ` [cocci] [v5] " Markus Elfring
2022-07-03 11:34 ` Markus Elfring [this message]
2022-07-03 10:50 ` [cocci] [PATCH v5] " Markus Elfring
2022-07-03 21:45 ` Julia Lawall
2022-07-04 17:16 ` [cocci] [v5] " Markus Elfring
2022-07-09 5:30 ` [cocci] [PATCH v5] " Markus Elfring
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=8ec4c66d-a315-5c64-7f7f-f707a175d56c@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=jeremy.lefaure@netatmo.com \
--cc=julia.lawall@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=nicolas.palix@imag.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;
as well as URLs for NNTP newsgroup(s).