From: Vaishali Thakkar <vaishali.thakkar@oracle.com>
To: mmarek@suse.com
Cc: Julia.Lawall@lip6.fr, Gilles.Muller@lip6.fr,
nicolas.palix@imag.fr, cocci@systeme.lip6.fr,
linux-kernel@vger.kernel.org, lars@metafoo.de
Subject: Re: [PATCH v2 3/3] Coccinelle: misc: Add support for devm variant in all modes
Date: Tue, 18 Oct 2016 22:35:36 +0530 [thread overview]
Message-ID: <58065660.2080609@oracle.com> (raw)
In-Reply-To: <5ed1989baa292520d4ed674580ced775a1ec2707.1476635073.git.vaishali.thakkar@oracle.com>
On Sunday 16 October 2016 10:37 PM, Vaishali Thakkar wrote:
> Add missing support for the devm_request_threaded_irq in
> the rules of context, report and org modes.
>
> Misc:
> ----
> To be consistent with other scripts, change confidence level
> of the script to 'Moderate'.
>
> Signed-off-by: Vaishali Thakkar <vaishali.thakkar@oracle.com>
> ---
> scripts/coccinelle/misc/irqf_oneshot.cocci | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/coccinelle/misc/irqf_oneshot.cocci b/scripts/coccinelle/misc/irqf_oneshot.cocci
> index 03b748d..f6c93fd 100644
> --- a/scripts/coccinelle/misc/irqf_oneshot.cocci
> +++ b/scripts/coccinelle/misc/irqf_oneshot.cocci
> @@ -5,7 +5,7 @@
> /// So pass the IRQF_ONESHOT flag in this case.
> ///
> //
> -// Confidence: Good
> +// Confidence: Moderate
> // Comments:
> // Options: --no-includes
>
> @@ -89,13 +89,21 @@ devm_request_threaded_irq@p(dev, irq, NULL, thread_fn,
> @depends on context@
> position p != {r1.p,r2.p};
> @@
> +(
> *request_threaded_irq@p(irq, NULL, ...)
> +|
> +*devm_request_threaded_irq@p(dev, irq, NULL, ...)
> +)
>
> @match depends on report || org@
> expression irq;
> position p != {r1.p,r2.p};
> @@
> +(
> request_threaded_irq@p(irq, NULL, ...)
> +|
> +devm_request_threaded_irq@p(dev, irq, NULL, ...)
> +)
Oh, my bad here. :(
Forgot the initialization of meta variables for the
arguments.
But I am wondering why coccicheck didn't fail here.
Isn't it suppose to give parsing errors? Or it doesn't
do that?
In any case, I am sorry for this. I'll send the revised
version of the patches.
> @script:python depends on org@
> p << match.p;
>
--
Vaishali
next prev parent reply other threads:[~2016-10-18 17:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 17:06 [PATCH v2 0/3] Coccinelle: misc: Improve the script for more accurate results Vaishali Thakkar
2016-10-16 17:07 ` [PATCH v2 3/3] Coccinelle: misc: Add support for devm variant in all modes Vaishali Thakkar
2016-10-18 17:01 ` Vaishali Thakkar
2016-10-18 17:05 ` Vaishali Thakkar [this message]
2016-10-18 17:10 ` Julia Lawall
2016-10-18 17:35 ` Vaishali Thakkar
2016-10-16 17:09 ` [PATCH v2 1/3] Coccinelle: misc: Improve the matching of rules Vaishali Thakkar
2016-10-16 17:10 ` [PATCH v2 2/3] Coccinelle: misc: Improve the result given by context mode Vaishali Thakkar
2016-10-18 16:34 ` [PATCH v2 0/3] Coccinelle: misc: Improve the script for more accurate results Julia Lawall
2016-10-18 16:53 ` Vaishali Thakkar
2016-10-18 17:01 ` Julia Lawall
2016-10-18 17:11 ` Vaishali Thakkar
2016-10-18 18:05 ` Julia Lawall
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=58065660.2080609@oracle.com \
--to=vaishali.thakkar@oracle.com \
--cc=Gilles.Muller@lip6.fr \
--cc=Julia.Lawall@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=nicolas.palix@imag.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;
as well as URLs for NNTP newsgroup(s).