From: Julia Lawall <julia.lawall@lip6.fr>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Yi Wang <wang.yi59@zte.com.cn>,
Michal Marek <michal.lkml@markovi.net>,
kernel-janitors@vger.kernel.org,
Nicolas Palix <nicolas.palix@imag.fr>,
linux-kernel@vger.kernel.org, cocci@systeme.lip6.fr,
Wen Yang <wen.yang99@zte.com.cn>
Subject: Re: [PATCH] coccinelle: put_device: reduce false positives
Date: Sat, 23 Mar 2019 20:06:54 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1903232104030.5660@hadrien> (raw)
In-Reply-To: <179bbdd1-3fcb-bba5-52b3-7f96973c7650@web.de>
[-- Attachment #1: Type: text/plain, Size: 523 bytes --]
On Sat, 23 Mar 2019, Markus Elfring wrote:
> > Don't complain about a return when this function returns "&pdev->dev".
>
> Would this information qualify to add the tag “Fixes” to the commit message?
Fixes tags relate to stable kernels, so that one can see which stable
kernels a particular patch should be propagated to. There is no need to
propagate patches on semantic patches to stable kernels. People who run
stable kernels are interested in their behavior, not the bug finding
rules that they contain.
julia
next prev parent reply other threads:[~2019-03-23 20:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1553321671-27749-1-git-send-email-wen.yang99@zte.com.cn>
2019-03-23 19:44 ` [PATCH] coccinelle: put_device: reduce false positives Markus Elfring
2019-03-23 20:06 ` Julia Lawall [this message]
2019-03-26 8:45 ` Dan Carpenter
2019-03-26 9:38 ` Julia Lawall
2019-03-26 10:11 ` Dan Carpenter
2019-03-26 10:15 ` Julia Lawall
2019-03-28 13:08 ` Masahiro Yamada
2019-03-28 14:19 ` Julia Lawall
2019-04-01 6:44 ` Coccinelle: " Markus Elfring
2019-04-01 20:04 ` 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=alpine.DEB.2.21.1903232104030.5660@hadrien \
--to=julia.lawall@lip6.fr \
--cc=Markus.Elfring@web.de \
--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 \
/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