From: Christoph Hellwig <hch@infradead.org>
To: Zhang Xiaoxu <zhangxiaoxu5@huawei.com>
Cc: linux-nvme@lists.infradead.org, hare@suse.de, hch@lst.de,
sagi@grimberg.me, kch@nvidia.com
Subject: Re: [-next v2] nvmet-auth: use kmemdup instead of kmalloc + memcpy
Date: Thu, 28 Jul 2022 09:07:01 -0700 [thread overview]
Message-ID: <YuK0JRw/9msWCyvw@infradead.org> (raw)
In-Reply-To: <20220726025632.1401689-1-zhangxiaoxu5@huawei.com>
On Tue, Jul 26, 2022 at 10:56:32AM +0800, Zhang Xiaoxu wrote:
> For code neat purpose, we can use kmemdup to replace
> kmalloc + memcpy.
Thanks, applied to nvme-5.20 after fixing the coding style.
prev parent reply other threads:[~2022-07-28 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 2:56 [-next v2] nvmet-auth: use kmemdup instead of kmalloc + memcpy Zhang Xiaoxu
2022-07-28 16:07 ` Christoph Hellwig [this message]
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=YuK0JRw/9msWCyvw@infradead.org \
--to=hch@infradead.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=zhangxiaoxu5@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