From: Markus Elfring <Markus.Elfring@web.de>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
Wen Yang <wen.yang99@zte.com.cn>,
Julia Lawall <Julia.Lawall@lip6.fr>
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,
Cheng Shengyu <cheng.shengyu@zte.com.cn>,
cocci@systeme.lip6.fr
Subject: Re: [v5] coccinelle: semantic code search for missing put_device()
Date: Sun, 17 Mar 2019 09:05:37 +0000 [thread overview]
Message-ID: <3562454b-36ff-3729-8d7c-c98e2b3f5767@web.de> (raw)
In-Reply-To: <CAK7LNASzd=bL1H34w-E_UD9x6w2=ObyS+EPDZ_jrvfV+ncw-yA@mail.gmail.com>
> Applied to linux-kbuild.
How does this information fit to the published sixth version
of the discussed script for the semantic patch language?
https://lore.kernel.org/cocci/HK0PR02MB36344E2B29CEB195892F6420B2610@HK0PR02MB3634.apcprd02.prod.outlook.com/
https://systeme.lip6.fr/pipermail/cocci/2019-February/005598.html
Are possible changes still in the waiting queue for a seventh variant?
https://lore.kernel.org/cocci/201902191014156680299@zte.com.cn/
Regards,
Markus
next prev parent reply other threads:[~2019-03-17 9:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1550217319-40418-1-git-send-email-wen.yang99@zte.com.cn>
2019-02-15 9:10 ` [PATCH v5] coccinelle: semantic code search for missing put_device() Markus Elfring
2019-02-15 12:52 ` [PATCH v5] Coccinelle: " Markus Elfring
2019-02-15 13:02 ` Julia Lawall
2019-02-15 13:15 ` [v5] " Markus Elfring
2019-02-15 13:15 ` Markus Elfring
2019-02-15 13:24 ` Julia Lawall
2019-02-15 13:54 ` Markus Elfring
[not found] ` <CAK7LNASzd=bL1H34w-E_UD9x6w2=ObyS+EPDZ_jrvfV+ncw-yA@mail.gmail.com>
2019-03-17 9:05 ` Markus Elfring [this message]
2019-03-23 16:17 ` [v5] coccinelle: " Markus Elfring
2019-03-26 6:54 ` Masahiro Yamada
2019-03-26 7:19 ` Julia Lawall
2019-03-26 9:14 ` Markus Elfring
2019-03-26 9:04 ` Markus Elfring
2019-03-26 9:52 ` Masahiro Yamada
2019-03-26 9:58 ` Julia Lawall
[not found] <201902161529041506841@zte.com.cn>
2019-02-16 8:09 ` [v5] Coccinelle: " Julia Lawall
2019-02-16 8:29 ` Markus Elfring
2019-02-16 8:32 ` Julia Lawall
2019-02-16 8:44 ` 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=3562454b-36ff-3729-8d7c-c98e2b3f5767@web.de \
--to=markus.elfring@web.de \
--cc=Julia.Lawall@lip6.fr \
--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=yamada.masahiro@socionext.com \
--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