From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@lip6.fr>, Coccinelle <cocci@systeme.lip6.fr>
Cc: LKML <linux-kernel@vger.kernel.org>,
Allison Randal <allison@lohutok.net>,
Enrico Weigelt <lkml@metux.net>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kate Stewart <kstewart@linuxfoundation.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <michal.lkml@markovi.net>,
Nicolas Palix <nicolas.palix@imag.fr>,
Thomas Gleixner <tglx@linutronix.de>,
Wen Yang <wen.yang99@zte.com.cn>, Yi Wang <wang.yi59@zte.com.cn>
Subject: Re: Coccinelle: pci_free_consistent: Checking when constraints
Date: Mon, 16 Sep 2019 08:24:49 +0200 [thread overview]
Message-ID: <7fc4c8fd-c00e-a455-29ff-ec016cbff08a@web.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1909082149100.2644@hadrien>
> If you had made your change and tested it, it's at least highly probable
> that you would understand why it is not sufficient as well.
Where do you expect to find the information how the Coccinelle software
should handle SmPL when constraints here finally?
> You first reflex when you have a question should be to try what you are
> wondering about, not to head for the mailing list.
>
> Please stop spreading misinformation.
* How will different application views influence the desired clarification of
software behaviour also for this use case?
* Can such an open issue be resolved better?
Regards,
Markus
prev parent reply other threads:[~2019-09-16 6:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-08 8:10 Markus Elfring
2019-09-08 8:23 ` Julia Lawall
2019-09-08 12:48 ` Markus Elfring
[not found] ` <alpine.DEB.2.21.1909082149100.2644@hadrien>
2019-09-09 10:40 ` Markus Elfring
2019-09-16 6:24 ` Markus Elfring [this message]
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=7fc4c8fd-c00e-a455-29ff-ec016cbff08a@web.de \
--to=markus.elfring@web.de \
--cc=Gilles.Muller@lip6.fr \
--cc=allison@lohutok.net \
--cc=cocci@systeme.lip6.fr \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@lip6.fr \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metux.net \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@imag.fr \
--cc=tglx@linutronix.de \
--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®