[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <VI1PR0402MB3485A113C5FB19DC556B678B98FB0@VI1PR0402MB3485.eurprd04.prod.outlook.com>
Date: Wed, 3 Jul 2019 17:10:26 +0000
From: Horia Geanta <horia.geanta@....com>
To: Fuqian Huang <huangfq.daxian@...il.com>
CC: Aymen Sghaier <aymen.sghaier@....com>,
Herbert Xu <herbert@...dor.apana.org.au>,
"David S . Miller" <davem@...emloft.net>,
Gonglei <arei.gonglei@...wei.com>,
"Michael S . Tsirkin" <mst@...hat.com>,
Jason Wang <jasowang@...hat.com>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>
Subject: Re: [PATCH v2 06/35] crypto: Use kmemdup rather than duplicating its
implementation
On 7/3/2019 7:27 PM, 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.
>
> Signed-off-by: Fuqian Huang <huangfq.daxian@...il.com>
Reviewed-by: Horia Geantă <horia.geanta@....com>
Thanks,
Horia
Powered by blists - more mailing lists