From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Adjustment for const qualification
Date: Wed, 15 Aug 2018 11:36:08 +0200 [thread overview]
Message-ID: <94cb119a-e880-2442-35e7-c1286ea8b032@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1808151127520.2309@hadrien>
>> How do you think about to try the following SmPL script variant out?
>>
>> @replacement@
>> @@
>> -const
>> +__genl_const
>> struct
>> (
>> genl_multicast_group
>> |genl_ops
>> )
>
> This is rejected by the semantic patch parser.
Can my update suggestion make sense if the parsing software
will be adjusted anyhow?
Does this variant need a small adjustment to get it working
with the current tool version?
Regards,
Markus
next prev parent reply other threads:[~2018-08-15 9:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 13:09 New release after 1.0.7? Luciano Coelho
2018-08-14 13:09 ` [Cocci] " Luciano Coelho
2018-08-14 13:19 ` Julia Lawall
2018-08-14 13:19 ` Julia Lawall
2018-08-14 13:32 ` Luciano Coelho
2018-08-14 13:32 ` Luciano Coelho
2018-08-14 13:43 ` Julia Lawall
2018-08-14 13:43 ` Julia Lawall
2018-08-14 14:39 ` Luciano Coelho
2018-08-14 14:39 ` Luciano Coelho
2018-08-16 7:05 ` Johannes Berg
2018-08-16 7:05 ` Johannes Berg
2018-08-16 7:09 ` Luciano Coelho
2018-08-15 8:55 ` [Cocci] Adjustment for const qualification SF Markus Elfring
2018-08-15 9:28 ` Julia Lawall
2018-08-15 9:36 ` SF Markus Elfring [this message]
2018-08-15 9:40 ` Julia Lawall
2018-08-16 5:45 ` SF Markus Elfring
2018-09-10 7:24 ` [Cocci] New release after 1.0.7? Johannes Berg
2018-09-10 7:24 ` Johannes Berg
2018-09-10 10:43 ` Julia Lawall
2018-09-10 10:43 ` Julia Lawall
2018-09-12 10:14 ` Julia Lawall
2018-09-12 10:14 ` Julia Lawall
2018-09-12 10:16 ` Johannes Berg
2018-09-12 10:16 ` Johannes Berg
2018-10-22 11:44 ` Arend van Spriel
2018-10-22 11:45 ` Johannes Berg
2018-10-22 19:49 ` Hauke Mehrtens
2018-10-22 20:46 ` Arend van Spriel
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=94cb119a-e880-2442-35e7-c1286ea8b032@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=cocci@systeme.lip6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.