From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>,
Wen Yang <wenyang@linux.alibaba.com>,
cocci@systeme.lip6.fr
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
"Gilles Muller" <Gilles.Muller@lip6.fr>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Masahiro Yamada" <yamada.masahiro@socionext.com>,
"Matthias Männich" <maennich@google.com>,
"Michal Marek" <michal.lkml@markovi.net>,
"Nicolas Palix" <nicolas.palix@imag.fr>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [v2] coccinelle: semantic patch to check for inappropriate do_div() calls
Date: Thu, 9 Jan 2020 13:00:45 +0100 [thread overview]
Message-ID: <e479c5c7-2556-eb77-9e9c-8833fb883a39@web.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2001091140380.10786@hadrien>
>> Thus I suggest now to split the source code search pattern into
>> four separate rules.
>
> Why?
Does the Coccinelle software ensure that a variable like “r.ul” contains
really useful data even if the expected branch of the SmPL disjunction
was occasionally not matched?
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>,
Wen Yang <wenyang@linux.alibaba.com>,
cocci@systeme.lip6.fr
Cc: kernel-janitors@vger.kernel.org,
"Michal Marek" <michal.lkml@markovi.net>,
"Gilles Muller" <Gilles.Muller@lip6.fr>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Nicolas Palix" <nicolas.palix@imag.fr>,
"Matthias Männich" <maennich@google.com>,
linux-kernel@vger.kernel.org,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [v2] coccinelle: semantic patch to check for inappropriate do_div() calls
Date: Thu, 09 Jan 2020 12:00:45 +0000 [thread overview]
Message-ID: <e479c5c7-2556-eb77-9e9c-8833fb883a39@web.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2001091140380.10786@hadrien>
>> Thus I suggest now to split the source code search pattern into
>> four separate rules.
>
> Why?
Does the Coccinelle software ensure that a variable like “r.ul” contains
really useful data even if the expected branch of the SmPL disjunction
was occasionally not matched?
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>,
Wen Yang <wenyang@linux.alibaba.com>,
cocci@systeme.lip6.fr
Cc: kernel-janitors@vger.kernel.org,
"Michal Marek" <michal.lkml@markovi.net>,
"Gilles Muller" <Gilles.Muller@lip6.fr>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Nicolas Palix" <nicolas.palix@imag.fr>,
"Matthias Männich" <maennich@google.com>,
linux-kernel@vger.kernel.org,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [Cocci] [v2] coccinelle: semantic patch to check for inappropriate do_div() calls
Date: Thu, 9 Jan 2020 13:00:45 +0100 [thread overview]
Message-ID: <e479c5c7-2556-eb77-9e9c-8833fb883a39@web.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2001091140380.10786@hadrien>
>> Thus I suggest now to split the source code search pattern into
>> four separate rules.
>
> Why?
Does the Coccinelle software ensure that a variable like “r.ul” contains
really useful data even if the expected branch of the SmPL disjunction
was occasionally not matched?
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2020-01-09 12:01 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 17:02 [PATCH v2] coccinelle: semantic patch to check for inappropriate do_div() calls Wen Yang
2020-01-07 17:02 ` [Cocci] " Wen Yang
2020-01-07 17:25 ` Julia Lawall
2020-01-07 17:25 ` [Cocci] " Julia Lawall
2020-01-10 13:11 ` Wen Yang
2020-01-10 13:11 ` [Cocci] " Wen Yang
2020-01-09 10:35 ` Markus Elfring
2020-01-09 10:35 ` [Cocci] " Markus Elfring
2020-01-09 10:35 ` Markus Elfring
2020-01-09 10:41 ` Julia Lawall
2020-01-09 10:41 ` [Cocci] " Julia Lawall
2020-01-09 10:41 ` Julia Lawall
2020-01-09 12:00 ` Markus Elfring [this message]
2020-01-09 12:00 ` [Cocci] [v2] " Markus Elfring
2020-01-09 12:00 ` Markus Elfring
2020-01-09 12:04 ` Julia Lawall
2020-01-09 12:04 ` [Cocci] " Julia Lawall
2020-01-09 12:04 ` Julia Lawall
2020-01-09 12:14 ` Markus Elfring
2020-01-09 12:14 ` [Cocci] " Markus Elfring
2020-01-09 12:14 ` Markus Elfring
2020-01-09 12:17 ` Julia Lawall
2020-01-09 12:17 ` [Cocci] " Julia Lawall
2020-01-09 12:17 ` Julia Lawall
2020-01-09 12:21 ` Markus Elfring
2020-01-09 12:21 ` [Cocci] " Markus Elfring
2020-01-09 12:21 ` Markus Elfring
2020-01-10 10:00 ` [PATCH v2] " Markus Elfring
2020-01-10 10:00 ` [Cocci] " Markus Elfring
2020-01-10 10:00 ` Markus Elfring
2020-01-10 12:34 ` Julia Lawall
2020-01-10 12:34 ` [Cocci] " Julia Lawall
2020-01-10 12:34 ` Julia Lawall
2020-01-10 15:46 ` [v2] coccinelle: semantic code search " Markus Elfring
2020-01-10 15:46 ` [Cocci] " Markus Elfring
2020-01-10 15:46 ` 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=e479c5c7-2556-eb77-9e9c-8833fb883a39@web.de \
--to=markus.elfring@web.de \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maennich@google.com \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@imag.fr \
--cc=tglx@linutronix.de \
--cc=wenyang@linux.alibaba.com \
--cc=yamada.masahiro@socionext.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.