From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Wen Yang <wen.yang99@zte.com.cn>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <michal.lkml@markovi.net>,
Nicolas Palix <nicolas.palix@imag.fr>,
Yi Wang <wang.yi59@zte.com.cn>,
Cheng Shengyu <cheng.shengyu@zte.com.cn>,
Ma Jiang <ma.jiang@zte.com.cn>,
LKML <linux-kernel@vger.kernel.org>,
Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [3/3] Coccinelle: pci_free_consistent: Extend when constraints for two SmPL ellipses
Date: Wed, 15 May 2019 10:36:52 +0200 [thread overview]
Message-ID: <bfde9b91-0c5d-31a0-4b1b-5f675152b2f8@web.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1905150808180.2591@hadrien>
>> 1, "id = (T2)(e)" is rare.
>
> Thanks for checking. I don't really care if it is rare.
I got related source code analysis concerns.
> There should not be much cost to this.
Each additional filter will influence the software run times and
possible results.
> On the other hand, I do care about causing false negatives.
Do you find the missing warning after the addition of such an exclusion
specification interesting?
Regards,
Markus
next prev parent reply other threads:[~2019-05-15 8:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201905151043340243098@zte.com.cn>
2019-05-15 6:10 ` [PATCH 3/3] Coccinelle: pci_free_consistent: Extend whenconstraints " Julia Lawall
2019-05-15 8:36 ` Markus Elfring [this message]
[not found] ` <alpine.DEB.2.20.1905151119070.3231@hadrien>
2019-05-15 9:40 ` [3/3] Coccinelle: pci_free_consistent: Extend when constraints " Markus Elfring
2019-05-15 10:19 ` Julia Lawall
2019-05-15 11:18 ` Markus Elfring
2019-05-15 6:48 ` Markus Elfring
2019-05-15 6:48 ` Markus Elfring
2019-05-15 7:48 ` Markus Elfring
2019-05-15 12:48 ` Markus Elfring
[not found] <201905151538552354689@zte.com.cn>
2019-05-15 8:06 ` 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=bfde9b91-0c5d-31a0-4b1b-5f675152b2f8@web.de \
--to=markus.elfring@web.de \
--cc=Gilles.Muller@lip6.fr \
--cc=cheng.shengyu@zte.com.cn \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=ma.jiang@zte.com.cn \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@imag.fr \
--cc=wang.yi59@zte.com.cn \
--cc=wen.yang99@zte.com.cn \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®