From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: zhong jiang <zhongjiang@huawei.com>
Cc: martin.petersen@oracle.com, don.brace@microsemi.com,
jejb@linux.vnet.ibm.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH v2] scsi: Use vmemdup_user to replace the open code
Date: Tue, 25 Sep 2018 20:45:05 -0400 [thread overview]
Message-ID: <yq17ej9hysu.fsf@oracle.com> (raw)
In-Reply-To: <1537286081-63081-1-git-send-email-zhongjiang@huawei.com> (zhong jiang's message of "Tue, 18 Sep 2018 23:54:41 +0800")
zhong,
> vmemdup_user is better than duplicating its implementation, So just
> replace the open code.
Applied to 4.20/scsi-queue, thanks!
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: zhong jiang <zhongjiang@huawei.com>
Cc: <martin.petersen@oracle.com>, <don.brace@microsemi.com>,
<jejb@linux.vnet.ibm.com>, <linux-scsi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [RESEND PATCH v2] scsi: Use vmemdup_user to replace the open code
Date: Tue, 25 Sep 2018 20:45:05 -0400 [thread overview]
Message-ID: <yq17ej9hysu.fsf@oracle.com> (raw)
In-Reply-To: <1537286081-63081-1-git-send-email-zhongjiang@huawei.com> (zhong jiang's message of "Tue, 18 Sep 2018 23:54:41 +0800")
zhong,
> vmemdup_user is better than duplicating its implementation, So just
> replace the open code.
Applied to 4.20/scsi-queue, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2018-09-26 0:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 15:54 [RESEND PATCH v2] scsi: Use vmemdup_user to replace the open code zhong jiang
2018-09-18 15:54 ` zhong jiang
2018-09-21 14:16 ` zhong jiang
2018-09-21 14:16 ` zhong jiang
2018-09-26 0:45 ` Martin K. Petersen [this message]
2018-09-26 0:45 ` Martin K. Petersen
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=yq17ej9hysu.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=don.brace@microsemi.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.