From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: [cocci] More benefits from higher level structures for coccicheck scripts?
Date: Fri, 21 Feb 2025 11:11:09 +0100 [thread overview]
Message-ID: <1fab8d2f-20e5-4e92-afb3-53167fecab54@web.de> (raw)
Hello,
Various source code was assigned to functions (or function-like macros).
Common functionality is stored at selected places.
Thus there is a desire to increase the corresponding usage.
Some scripts were constructed also according to the means of the semantic
patch language.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/dev-tools/coccinelle.rst?h=v6.14-rc3#n71
It can be seen that some of these SmPL scripts share also program structures.
* Operation modes need to be determined.
* Special source code items should be detected somehow.
* Data output should be provided.
Would you be looking for the support of higher level structures for
coccicheck scripts?
Is there a need for placeholders (or variables) which could be filled from
other advanced information sources so that selected data processing
will eventually not be mapped to separate SmPL script files to achieve more
desirable transformations?
Regards,
Markus
reply other threads:[~2025-02-21 10:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1fab8d2f-20e5-4e92-afb3-53167fecab54@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).