From: Christoph Hellwig <hch@lst.de>
To: Chen Zhou <chenzhou10@huawei.com>
Cc: linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
hch@lst.de, chaitanya.kulkarni@wdc.com, sagi@grimberg.me
Subject: Re: [PATCH -next] nvmet: replace kstrndup() with kmemdup_nul()
Date: Tue, 12 May 2020 18:14:11 +0200 [thread overview]
Message-ID: <20200512161411.GC6049@lst.de> (raw)
In-Reply-To: <20200508115906.165223-1-chenzhou10@huawei.com>
On Fri, May 08, 2020 at 07:59:06PM +0800, Chen Zhou wrote:
> It is more efficient to use kmemdup_nul() if the size is known exactly.
>
> The doc in kernel:
> "Note: Use kmemdup_nul() instead if the size is known exactly."
>
> Signed-off-by: Chen Zhou <chenzhou10@huawei.com>
Thanks,
applied to nvme-5.8.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Chen Zhou <chenzhou10@huawei.com>
Cc: hch@lst.de, sagi@grimberg.me, chaitanya.kulkarni@wdc.com,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] nvmet: replace kstrndup() with kmemdup_nul()
Date: Tue, 12 May 2020 18:14:11 +0200 [thread overview]
Message-ID: <20200512161411.GC6049@lst.de> (raw)
In-Reply-To: <20200508115906.165223-1-chenzhou10@huawei.com>
On Fri, May 08, 2020 at 07:59:06PM +0800, Chen Zhou wrote:
> It is more efficient to use kmemdup_nul() if the size is known exactly.
>
> The doc in kernel:
> "Note: Use kmemdup_nul() instead if the size is known exactly."
>
> Signed-off-by: Chen Zhou <chenzhou10@huawei.com>
Thanks,
applied to nvme-5.8.
next prev parent reply other threads:[~2020-05-12 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 11:59 [PATCH -next] nvmet: replace kstrndup() with kmemdup_nul() Chen Zhou
2020-05-08 11:59 ` Chen Zhou
2020-05-12 16:14 ` Christoph Hellwig [this message]
2020-05-12 16:14 ` Christoph Hellwig
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=20200512161411.GC6049@lst.de \
--to=hch@lst.de \
--cc=chaitanya.kulkarni@wdc.com \
--cc=chenzhou10@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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.