From: Markus Elfring <Markus.Elfring@web.de>
To: info@metux.net
Cc: linux-kernel@vger.kernel.org, Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] [PATCH] scripts: coccinelle: add check for uncessary double unlikely() calls
Date: Mon, 15 Jul 2019 21:50:25 +0200 [thread overview]
Message-ID: <4b14aac8-af14-3599-0d66-7ebde8b06ac1@web.de> (raw)
In-Reply-To: <1559767582-11081-1-git-send-email-info@metux.net>
My software development attention was caught also by your proposal.
I would appreciate a message subject without a typo.
> +virtual patch
> +virtual context
> +virtual org
> +virtual report
These metavariables are not used in the subsequent code in this approach
for the semantic patch language.
Fine-tuning might become relevant also for the change specifications.
https://lore.kernel.org/lkml/1559767582-11081-1-git-send-email-info@metux.net/
Would you like to contribute an extended script version?
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
parent reply other threads:[~2019-07-15 19:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1559767582-11081-1-git-send-email-info@metux.net>]
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=4b14aac8-af14-3599-0d66-7ebde8b06ac1@web.de \
--to=markus.elfring@web.de \
--cc=cocci@systeme.lip6.fr \
--cc=info@metux.net \
--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 NNTP newsgroup(s).