From: Markus Elfring <Markus.Elfring@web.de>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Yi Wang <wang.yi59@zte.com.cn>,
kernel-janitors@vger.kernel.org,
Michal Marek <michal.lkml@markovi.net>,
Wen Yang <yellowriver2010@hotmail.com>,
Nicolas Palix <nicolas.palix@imag.fr>,
linux-kernel@vger.kernel.org, cocci@systeme.lip6.fr,
Cheng Shengyu <cheng.shengyu@zte.com.cn>,
Wen Yang <wen.yang99@zte.com.cn>
Subject: Re: [Cocci] [v5] coccinelle: semantic code search for missingput_device()
Date: Sat, 16 Feb 2019 10:20:41 +0100 [thread overview]
Message-ID: <8ba4643b-496e-597f-32e1-c14b8e46880c@web.de> (raw)
In-Reply-To: <20190216090658.lsfhvtllwnzj3675@ninjato>
>>> We don't need perfection.
>>
>> I guess that you noticed in the meantime that I dare to propose
>> more software development efforts in such a direction.
>
> Yes, this is noticable.
I am curious then if remaining change suggestions will be picked up
by more software developers and reviewers.
> It is your choice, however, other people may have their reasons
> for other choices...
Yes, of course.
>>> We need more to eliminate the memory leaks.
>
> ... like this one.
>
>> Will this view evolve into further helpful and constructive clarifications?
>
> Given my above, what is the evaluation of the same question to yourself?
* I hope that my contributions can improve the situation also
for this software area.
* Existing development tools will evolve further as usual.
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-02-16 9:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201902161633004137519@zte.com.cn>
2019-02-16 8:36 ` [Cocci] [v5] coccinelle: semantic code search for missingput_device() Julia Lawall
2019-02-16 8:41 ` Julia Lawall
2019-02-16 8:57 ` Markus Elfring
2019-02-16 9:06 ` Wolfram Sang
2019-02-16 9:20 ` Markus Elfring [this message]
[not found] <201902161504357846572@zte.com.cn>
2019-02-16 8:09 ` Markus Elfring
2019-02-16 8:34 ` Julia Lawall
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=8ba4643b-496e-597f-32e1-c14b8e46880c@web.de \
--to=markus.elfring@web.de \
--cc=cheng.shengyu@zte.com.cn \
--cc=cocci@systeme.lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@imag.fr \
--cc=wang.yi59@zte.com.cn \
--cc=wen.yang99@zte.com.cn \
--cc=wsa@the-dreams.de \
--cc=yellowriver2010@hotmail.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;
as well as URLs for NNTP newsgroup(s).