From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@lip6.fr>,
Coccinelle <cocci@systeme.lip6.fr>,
kernel-janitors@vger.kernel.org
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>
Subject: Re: Adjusting SmPL script “ptr_ret.cocci”?
Date: Sat, 7 Sep 2019 18:20:02 +0200 [thread overview]
Message-ID: <a50cebe5-4aae-ea93-1920-d5743435cd1d@web.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1909071804090.2562@hadrien>
>> How do you think about to reduce subsequent SmPL rules also according to
>> a possible recombination of affected implementation details?
>
> There is not going to be any change with respect to this issue.
I am curious if the software situation will be reconsidered any further
under other circumstances.
> It's fine when replacing one statement by another, but introduces complexity
> when removing something more complex.
Thanks for such information.
> And there's not point to have something that works in only one special case.
Will corresponding software development concerns be eventually discussed
a bit more?
Regards,
Markus
next prev parent reply other threads:[~2019-09-07 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-07 14:54 Markus Elfring
2019-09-07 16:05 ` Julia Lawall
2019-09-07 16:20 ` Markus Elfring [this message]
2019-09-07 16:40 ` [PATCH] Coccinelle: Reduce rules in SmPL script “ptr_ret.cocci” 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=a50cebe5-4aae-ea93-1920-d5743435cd1d@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=kernel-janitors@vger.kernel.org \
--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=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
Powered by JetHome