From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr, kernel-janitors@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [cocci] Passing code replacements by APIs (for SmPL)?
Date: Thu, 26 Jun 2025 13:18:54 +0200 [thread overview]
Message-ID: <5682c295-0c4a-41e9-bf80-fd14fd5c94db@web.de> (raw)
In-Reply-To: <481faa1d-7171-4657-8dc0-c37b153e6eaa@web.de>
> Would you become interested to convert contents from any header (or source) files
> into more advanced transformation approaches?
I demonstrated that expressions can be extracted from selected function implementations
also by the means of the semantic patch language.
https://lore.kernel.org/cocci/481faa1d-7171-4657-8dc0-c37b153e6eaa@web.de/
https://sympa.inria.fr/sympa/arc/cocci/2025-06/msg00044.html
Now I am looking again for further software extension possibilities.
1. I would like to sort found expressions by decreasing complexity.
2. Some expressions will probably refer to known function (or macro) calls.
How can corresponding identifiers be replaced by previously determined source code?
Regards,
Markus
prev parent reply other threads:[~2025-06-26 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 7:30 [cocci] Passing code replacements by APIs (for SmPL)? Markus Elfring
2025-06-23 8:05 ` Markus Elfring
2025-06-26 11:18 ` 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=5682c295-0c4a-41e9-bf80-fd14fd5c94db@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).