From: Markus Elfring <Markus.Elfring@web.de>
To: Wen Yang <wen.yang99@zte.com.cn>, Julia Lawall <julia.lawall@lip6.fr>
Cc: 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>,
Coccinelle <cocci@systeme.lip6.fr>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [3/3] Coccinelle: pci_free_consistent: Extend when constraints for two SmPL ellipses
Date: Wed, 15 May 2019 09:48:05 +0200 [thread overview]
Message-ID: <647104b8-3ee6-6317-0560-f02443192e65@web.de> (raw)
In-Reply-To: <39c4150c-b238-a0b4-19b4-6215012bb497@web.de>
>> But with your modified SmPL, we can't find the bug.
>
> I do not see a difference here.
I have accidentally overlooked to pass the parameter “-D report”
to the spatch program.
Now I notice also an unexpected and undesirable difference for your test example
after the suggested addition of exclusion specifications.
> - I wonder also about this situation then.
How should the software behaviour be improved finally?
Will we need to work with any SmPL script versions in parallel
for selected source code analysis configurations?
Regards,
Markus
next prev parent reply other threads:[~2019-05-15 7:48 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 ` [3/3] Coccinelle: pci_free_consistent: Extend when constraints " Markus Elfring
[not found] ` <alpine.DEB.2.20.1905151119070.3231@hadrien>
2019-05-15 9:40 ` 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 [this message]
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=647104b8-3ee6-6317-0560-f02443192e65@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®