From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>,
Denis Efremov <efremov@linux.com>,
Coccinelle <cocci@systeme.lip6.fr>
Cc: Gilles Muller <Gilles.Muller@lip6.fr>,
Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Nicolas Palix <nicolas.palix@imag.fr>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [v2 1/4] coccinelle: api: extend memdup_user transformation with GFP_USER
Date: Sat, 18 Jul 2020 14:14:20 +0200 [thread overview]
Message-ID: <0a961d1e-6bd2-45fd-113e-9258fe00a16a@web.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2007181034530.2538@hadrien>
> You proposed essentially \( A \| B \) \( | C \| \)
Will the software development attention grow for a topic
like “Extend support for handling of optional source code parts”?
https://github.com/coccinelle/coccinelle/issues/53
How do you think about another tiny example script for the semantic patch language?
@display@
constant A, B;
@@
*A
?| B
elfring@Sonne:~/Projekte/Coccinelle/Probe> spatch --parse-cocci optional_disjunction_test3-20200718.cocci
…
warning: incompatible arity found on line 4
incompatible minus and plus code starting on lines 4 and 4
Regards,
Markus
next prev parent reply other threads:[~2020-07-18 12:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 5:56 [v2 1/4] coccinelle: api: extend memdup_user transformation with GFP_USER Markus Elfring
2020-07-18 6:45 ` Julia Lawall
2020-07-18 7:09 ` Markus Elfring
2020-07-18 8:41 ` Julia Lawall
2020-07-18 9:16 ` Markus Elfring
2020-07-18 12:14 ` Markus Elfring [this message]
2020-07-18 13:11 ` Denis Efremov
2020-07-18 13:29 ` Julia Lawall
2020-07-19 8:36 ` 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=0a961d1e-6bd2-45fd-113e-9258fe00a16a@web.de \
--to=markus.elfring@web.de \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=efremov@linux.com \
--cc=julia.lawall@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--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