From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: cocci@inria.fr
Subject: Re: [cocci] Searching for repeated source code with SmPL?
Date: Wed, 22 May 2024 18:06:49 +0200 [thread overview]
Message-ID: <c46a86a3-aa3d-4934-85d0-801915c9edca@web.de> (raw)
In-Reply-To: <d51167c4-af9f-6b82-9ab8-9a807c98186b@inria.fr>
>>> --noloops mean that the back edge of a loop is ignored.
>>
>> Should the program parameter “--no-loops” influence also the handling
>> of Linux “iterators” (like “list_for_each_entry_safe”) anyhow?
>
> No idea.
How do you think about to take another look at further diff outputs
which can be generated by a simple SmPL script example?
Analysing statement sequences in consistent ways (with SmPL)?
https://lore.kernel.org/cocci/4c2812f7-d54d-412b-ac79-c650ceedcecd@web.de/
https://sympa.inria.fr/sympa/arc/cocci/2024-05/msg00076.html
Source files for corresponding clarification opportunities:
* ath6kl_set_multicast_list()
https://elixir.bootlin.com/linux/v6.9.1/source/drivers/net/wireless/ath/ath6kl/main.c#L1232
* batadv_frag_merge_packets()
https://elixir.bootlin.com/linux/v6.9.1/source/net/batman-adv/fragmentation.c#L258
* iavf_reset_task()
https://elixir.bootlin.com/linux/v6.9.1/source/drivers/net/ethernet/intel/iavf/iavf_main.c#L3097
* bch_pending_bdevs_cleanup()
https://elixir.bootlin.com/linux/v6.9.1/source/drivers/md/bcache/super.c#L2691
Regards,
Markus
prev parent reply other threads:[~2024-05-22 16:06 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 10:08 [cocci] Searching for repeated source code with SmPL? Markus Elfring
2024-05-06 10:09 ` Julia Lawall
2024-05-06 11:03 ` Markus Elfring
2024-05-06 12:10 ` Markus Elfring
2024-05-06 12:16 ` Julia Lawall
2024-05-06 12:40 ` Markus Elfring
2024-05-11 15:36 ` Markus Elfring
2024-05-11 16:04 ` Julia Lawall
2024-05-11 16:35 ` Markus Elfring
2024-05-11 16:37 ` Julia Lawall
2024-05-11 17:02 ` Markus Elfring
2024-05-11 17:12 ` Julia Lawall
2024-05-11 17:21 ` Markus Elfring
2024-05-11 17:33 ` Julia Lawall
2024-05-12 6:48 ` Markus Elfring
2024-05-12 7:34 ` Julia Lawall
2024-05-12 8:01 ` Markus Elfring
2024-05-12 8:10 ` Julia Lawall
2024-05-12 8:33 ` Markus Elfring
2024-05-12 9:17 ` Julia Lawall
2024-05-12 9:30 ` Markus Elfring
2024-05-13 9:34 ` Markus Elfring
2024-05-12 11:24 ` Markus Elfring
2024-05-12 12:53 ` Julia Lawall
2024-05-12 13:07 ` Markus Elfring
2024-05-12 13:13 ` Julia Lawall
2024-05-12 13:22 ` Markus Elfring
2024-05-12 14:51 ` Markus Elfring
2024-05-12 14:57 ` Julia Lawall
2024-05-11 7:15 ` Markus Elfring
2024-05-22 8:20 ` Markus Elfring
2024-05-22 8:24 ` Julia Lawall
2024-05-22 8:44 ` Markus Elfring
2024-05-22 13:12 ` Markus Elfring
2024-05-22 15:34 ` Julia Lawall
2024-05-22 16:06 ` Markus Elfring [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=c46a86a3-aa3d-4934-85d0-801915c9edca@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=julia.lawall@inria.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.