[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231220081924.39b96ec4@xps-13>
Date: Wed, 20 Dec 2023 08:19:24 +0100
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Rafał Miłecki <zajec5@...il.com>
Cc: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>, Rob Herring
<robh+dt@...nel.org>, Krzysztof Kozlowski
<krzysztof.kozlowski+dt@...aro.org>, Conor Dooley <conor+dt@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Michael Walle
<michael@...le.cc>, linux-mtd@...ts.infradead.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, u-boot@...ts.denx.de, Rafał Miłecki <rafal@...ecki.pl>
Subject: Re: [PATCH V2 4/5] nvmem: u-boot-env: improve coding style
Hi Rafał,
zajec5@...il.com wrote on Tue, 19 Dec 2023 18:40:24 +0100:
> From: Rafał Miłecki <rafal@...ecki.pl>
>
> 1. Prefer kzalloc() over kcalloc()
> See memory-allocation.rst which says: "to be on the safe side it's
> best to use routines that set memory to zero, like kzalloc()"
> 2. Drop dev_err() for u_boot_env_add_cells() fail
> It can fail only on -ENOMEM. We don't want to print error then.
> 3. Add extra "crc32_addr" variable
> It makes code reading header's crc32 easier to understand / review.
>
> Signed-off-by: Rafał Miłecki <rafal@...ecki.pl>
Looks much nicer :)
Reviewed-by: Miquel Raynal <miquel.raynal@...tlin.com>
Thanks,
Miquèl
Powered by blists - more mailing lists