From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: cocci@systeme.lip6.fr
Subject: Re: [Cocci] How to replace obsolete #ifdef's?
Date: Fri, 7 Jun 2019 19:26:22 +0200 [thread overview]
Message-ID: <301dcd73-1290-3768-080e-101e78893675@web.de> (raw)
In-Reply-To: <alpine.DEB.2.20.1906071833010.14523@hadrien>
>> Will similar software updates become more challenging for the initially
>> described handling of designated initialisers for known data structures?
>
> This is in the spirit of the solution I already proposed.
How do you think about the following SmPL transformation approach?
@replacement@
constant text;
expression value;
identifier my_name;
type driver_type;
@@
static driver_type my_name =
{
.driver =
{
-.name = text,
+.name = text,
.of_match_table =
+ of_match_ptr(
value
+ )
,
}, ...
};
Test result:
elfring@Sonne:~/Projekte/Linux/next-patched> spatch ~/Projekte/Coccinelle/Probe/Weigelt5.cocci sound/soc/codecs/pcm3060-i2c.c
…
@@ -43,10 +43,10 @@ MODULE_DEVICE_TABLE(of, pcm3060_of_match
#endif /* CONFIG_OF */
static struct i2c_driver pcm3060_i2c_driver = {
+#ifdef CONFIG_OF
.driver = {
.name = "pcm3060",
-#ifdef CONFIG_OF
- .of_match_table = pcm3060_of_match,
+ .of_match_table = of_match_ptr(pcm3060_of_match),
#endif /* CONFIG_OF */
},
.id_table = pcm3060_i2c_id,
I would find it questionable that the software combination
“Coccinelle 1.0.7-00206-gfdcc6d79 (OCaml 4.07.1)” suggests to move
a conditional preprocessor statement to an other source code place.
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-06-07 17:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 16:25 [Cocci] how to replace obsolete #ifdef's Enrico Weigelt, metux IT consult
2019-06-05 19:51 ` [Cocci] How to replace obsolete #ifdef's? Markus Elfring
2019-06-05 20:52 ` [Cocci] how to replace obsolete #ifdef's Julia Lawall
2019-06-05 21:42 ` Enrico Weigelt, metux IT consult
2019-06-06 5:46 ` Julia Lawall
2019-06-06 9:30 ` [Cocci] How to replace obsolete #ifdef's? Markus Elfring
2019-06-06 10:34 ` Julia Lawall
2019-06-06 14:20 ` Markus Elfring
2019-06-06 15:34 ` David Young
2019-06-07 12:01 ` Enrico Weigelt, metux IT consult
2019-06-07 12:30 ` Julia Lawall
2019-06-06 9:15 ` Markus Elfring
2019-06-06 9:39 ` Julia Lawall
2019-06-07 12:05 ` Enrico Weigelt, metux IT consult
2019-06-07 12:32 ` Julia Lawall
2019-06-07 13:40 ` Markus Elfring
2019-06-07 16:33 ` Julia Lawall
2019-06-07 17:26 ` Markus Elfring [this message]
2019-06-07 17:36 ` Markus Elfring
2019-06-07 18:48 ` Markus Elfring
2019-06-07 18:59 ` Julia Lawall
2019-06-08 7:49 ` [Cocci] Handling of designated initialisers by SmPL? 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=301dcd73-1290-3768-080e-101e78893675@web.de \
--to=markus.elfring@web.de \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@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 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).