[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <843fda3c-f1bd-61e0-e94d-38026ad98e5f@arista.com>
Date: Fri, 26 Aug 2022 15:42:09 +0100
From: Dmitry Safonov <dima@...sta.com>
To: Dan Carpenter <dan.carpenter@...cle.com>, kbuild@...ts.01.org,
Eric Dumazet <edumazet@...gle.com>,
"David S. Miller" <davem@...emloft.net>,
linux-kernel@...r.kernel.org
Cc: lkp@...el.com, kbuild-all@...ts.01.org, netdev@...r.kernel.org,
Andy Lutomirski <luto@...capital.net>,
Ard Biesheuvel <ardb@...nel.org>,
Bob Gilligan <gilligan@...sta.com>,
David Ahern <dsahern@...nel.org>,
Eric Biggers <ebiggers@...nel.org>,
Francesco Ruggeri <fruggeri@...sta.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
Ivan Delalande <colona@...sta.com>,
Jakub Kicinski <kuba@...nel.org>,
Leonard Crestez <cdleonard@...il.com>,
Paolo Abeni <pabeni@...hat.com>,
Salam Noureddine <noureddine@...sta.com>,
Shuah Khan <skhan@...uxfoundation.org>,
linux-crypto@...r.kernel.org
Subject: Re: [PATCH 02/31] crypto_pool: Add crypto_pool_reserve_scratch()
Hi Dan,
On 8/22/22 11:45, Dan Carpenter wrote:
> Hi Dmitry,
[..]
> "err" not set. It was supposed to be set to zero at the start. But
> better to say "ret = i;" here maybe?
>
> Why is i unsigned? It leads to unsightly casts. Presumably some static
> checker insists on this... :/
Thanks! Will be addressed/reworked in v2.
Thank you,
Dmitry
Powered by blists - more mailing lists