From: Markus Elfring <Markus.Elfring@web.de>
To: Qiang Zhang <Qiang.Zhang@windriver.com>, linux-usb@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>,
Felipe Balbi <balbi@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kyungtae Kim <kt0755@gmail.com>
Subject: Re: usb: gadget: function: printer: Fix use-after-free in __lock_acquire()
Date: Mon, 08 Jun 2020 10:55:13 +0000 [thread overview]
Message-ID: <ae59cac9-d770-36bd-ccb2-e5e442bd5e0a@web.de> (raw)
In-Reply-To: <DM5PR11MB205835FB50BA296232BC3163FF850@DM5PR11MB2058.namprd11.prod.outlook.com>
> I don't need to add Fix tag to view the code.
I have got understanding difficulties for this kind of feedback.
How much do you care for corresponding patch review concerns?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id¯7b4801030c07637840191c69eb666917e4135d#n183
Regards,
Markus
next prev parent reply other threads:[~2020-06-08 10:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 8:57 [PATCH] usb: gadget: function: printer: Fix use-after-free in __lock_acquire() Markus Elfring
2020-06-05 9:14 ` Greg Kroah-Hartman
2020-06-08 6:54 ` 回复: [PATCH] usb: gadget: function: printer: =?gb2312?B?IEZpeCB1c2UtYWZ Zhang, Qiang
2020-06-08 10:55 ` Markus Elfring [this message]
2020-06-08 11:01 ` usb: gadget: function: printer: Fix use-after-free in __lock_acquire() Greg Kroah-Hartman
2020-06-28 13:43 ` [PATCH] usb: gadget: function: printer: The device interface is reset and should return error co Markus Elfring
2020-06-28 14:13 ` Greg Kroah-Hartman
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=ae59cac9-d770-36bd-ccb2-e5e442bd5e0a@web.de \
--to=markus.elfring@web.de \
--cc=Qiang.Zhang@windriver.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kt0755@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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).