From: Markus Elfring <Markus.Elfring@web.de>
To: Wen Yang <wen.yang99@zte.com.cn>, linuxppc-dev@lists.ozlabs.org
Cc: Yi Wang <wang.yi59@zte.com.cn>,
Cheng Shengyu <cheng.shengyu@zte.com.cn>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Scott Wood <oss@buserror.net>, Paul Mackerras <paulus@samba.org>,
Xue Zhihong <xue.zhihong@zte.com.cn>
Subject: Re: [1/2] powerpc/83xx: fix use-after-free in mpc831x_usb_cfg()
Date: Wed, 10 Jul 2019 11:24:45 +0200 [thread overview]
Message-ID: <ef968d9a-785e-dbf7-dfe6-9572fc241e63@web.de> (raw)
In-Reply-To: <201907101533443009168@zte.com.cn>
> we developed a coccinelle script to detect such problems.
How do you think about to give any attribution to this development software
in your commit descriptions?
> After a period of testing, we will send it to the LMKL mailing list later.
I am also curious then on how this area will evolve further.
Regards,
Markus
next prev parent reply other threads:[~2019-07-10 9:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1562670768-23178-1-git-send-email-wen.yang99@zte.com.cn>
2019-07-09 11:12 ` [PATCH 1/2] powerpc/83xx: fix use-after-free in mpc831x_usb_cfg() Wen Yang
2019-07-10 7:19 ` [1/2] " Markus Elfring
2019-07-10 7:33 ` wen.yang99
2019-07-10 9:24 ` Markus Elfring [this message]
2019-07-10 15:15 ` Coccinelle: Checking of_node_put() calls with SmPL Markus Elfring
2019-07-11 6:35 ` wen.yang99
2019-07-11 6:46 ` Julia Lawall
2019-07-11 9:33 ` Markus Elfring
2019-07-11 9:04 ` Markus Elfring
2019-07-11 14:41 ` Tyrel Datwyler
2019-07-09 11:12 ` [PATCH 2/2] powerpc/83xx: cleanup error paths in mpc831x_usb_cfg() Wen Yang
2019-07-09 16:14 ` [PATCH 0/2] fix use-after-free in mpc831x_usb_cfg() and do some cleanups 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=ef968d9a-785e-dbf7-dfe6-9572fc241e63@web.de \
--to=markus.elfring@web.de \
--cc=cheng.shengyu@zte.com.cn \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oss@buserror.net \
--cc=paulus@samba.org \
--cc=wang.yi59@zte.com.cn \
--cc=wen.yang99@zte.com.cn \
--cc=xue.zhihong@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;
as well as URLs for NNTP newsgroup(s).