From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: zhong jiang <zhongjiang@huawei.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
<martin.petersen@oracle.com>, <Don.Brace@microchip.com>,
<don.brace@microsemi.com>, <jejb@linux.vnet.ibm.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] scsi: Use vmemdup_user to replace the open code
Date: Tue, 18 Sep 2018 11:09:24 -0400 [thread overview]
Message-ID: <yq11s9qrgez.fsf@oracle.com> (raw)
In-Reply-To: <5BA11315.4060908@huawei.com> (zhong jiang's message of "Tue, 18 Sep 2018 23:00:37 +0800")
Hi Zhong,
> Can you pick up the patch?
Please submit SCSI patches to linux-scsi@vger.kernel.org so they get
tracked in patchwork.
Thank you!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2018-09-18 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 12:43 [PATCH v2] scsi: Use vmemdup_user to replace the open code zhong jiang
2018-08-13 14:20 ` Don.Brace
2018-08-23 11:38 ` zhong jiang
2018-09-18 15:00 ` zhong jiang
2018-09-18 15:09 ` Martin K. Petersen [this message]
2018-09-18 15:13 ` zhong jiang
2018-09-18 15:10 ` Greg KH
2018-09-18 15:34 ` zhong jiang
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=yq11s9qrgez.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=Don.Brace@microchip.com \
--cc=don.brace@microsemi.com \
--cc=gregkh@linuxfoundation.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zhongjiang@huawei.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