From: Wolfram Sang <wsa@the-dreams.de>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
Wen Yang <wen.yang99@zte.com.cn>, 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,
Cheng Shengyu <cheng.shengyu@zte.com.cn>,
cocci@systeme.lip6.fr
Subject: Re: [Cocci] [v5] coccinelle: semantic code search for missingput_device()
Date: Sat, 16 Feb 2019 10:06:58 +0100 [thread overview]
Message-ID: <20190216090658.lsfhvtllwnzj3675@ninjato> (raw)
In-Reply-To: <992b8c6f-614d-b379-6352-30b36ac9d0d8@web.de>
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
Hi,
On Sat, Feb 16, 2019 at 09:57:54AM +0100, Markus Elfring wrote:
> > 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. It is your choice, however, other people may
have their reasons for other choices...
> > 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?
Regards,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-16 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201902161633004137519@zte.com.cn>
2019-02-16 8:36 ` [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 [this message]
2019-02-16 9:20 ` [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=20190216090658.lsfhvtllwnzj3675@ninjato \
--to=wsa@the-dreams.de \
--cc=Markus.Elfring@web.de \
--cc=cheng.shengyu@zte.com.cn \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@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=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).