From: Bob Copeland <me@bobcopeland.com>
To: Fuqian Huang <huangfq.daxian@gmail.com>
Cc: linux-karma-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 32/35] omfs: Use kmemdup rather than duplicating its implementation
Date: Wed, 3 Jul 2019 12:57:04 -0400 [thread overview]
Message-ID: <20190703165704.GC4930@localhost> (raw)
In-Reply-To: <20190703163158.937-1-huangfq.daxian@gmail.com>
On Thu, Jul 04, 2019 at 12:31:58AM +0800, Fuqian Huang wrote:
> kmemdup is introduced to duplicate a region of memory in a neat way.
> Rather than kmalloc/kzalloc + memcpy, which the programmer needs to
> write the size twice (sometimes lead to mistakes), kmemdup improves
> readability, leads to smaller code and also reduce the chances of mistakes.
> Suggestion to use kmemdup rather than using kmalloc/kzalloc + memcpy.
Acked-by: Bob Copeland <me@bobcopeland.com>
--
Bob Copeland %% https://bobcopeland.com/
prev parent reply other threads:[~2019-07-03 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 16:31 [PATCH v2 32/35] omfs: Use kmemdup rather than duplicating its implementation Fuqian Huang
2019-07-03 16:57 ` Bob Copeland [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=20190703165704.GC4930@localhost \
--to=me@bobcopeland.com \
--cc=huangfq.daxian@gmail.com \
--cc=linux-karma-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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