From: Tobias Deiminger <tobias.deiminger@posteo.de>
To: cocci@inria.fr
Subject: Re: [cocci] Matching a specific declarer?
Date: Mon, 01 Dec 2025 16:53:22 +0000 [thread overview]
Message-ID: <d842430fabc5cfbd805bdf6c8da82ec1@posteo.de> (raw)
In-Reply-To: <6bf5d8ea-5d04-4851-b464-19d2f76379f8@web.de>
Am 01.12.2025 17:00 schrieb Markus Elfring:
> [...]
>> but actually stumbled upon the issue in a simpler case: I searched for
>> all occurrences of DEVICE_ATTR_RO(attr) in the Linux kernel,
>
> Will it become more interesting to clarify your own source code search
> approaches?
Sorry, not sure I understand the question. Is there anything I should
do, or should avoid to do, or tell about?
If I manage to compile meaningful results until next week, I maybe add
some words about the code search approach to my LPC talk:
https://lpc.events/event/19/contributions/2198/
>> but actually found every place where *any* macro was used to declare
>> something.
>
> Would you be looking for any better documentation also in this
> application area?
You mean better Coccinelle documentation? I think it's ok. This list is
very responsive and helpful, that more than compensates for gaps in
documentation, if any. Also my use case is in the niche of a niche, so
really not demanding anything.
>> PS: I'm using spatch 1.3 from Debian trixie.
>
> It might become also interesting with which delay subsequent software
> tool revisions
> will be usable.
Which revisions of which tool do you mean?
Tobias
next prev parent reply other threads:[~2025-12-01 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 15:28 [cocci] bug: Matching a specific declarer actually matches any declarer Tobias Deiminger
2025-12-01 15:35 ` Julia Lawall
2025-12-01 16:18 ` Tobias Deiminger
2025-12-01 16:00 ` [cocci] Matching a specific declarer? Markus Elfring
2025-12-01 16:53 ` Tobias Deiminger [this message]
2025-12-01 17:21 ` 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=d842430fabc5cfbd805bdf6c8da82ec1@posteo.de \
--to=tobias.deiminger@posteo.de \
--cc=cocci@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox