[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZP/iw6jvHrlBavdK@gondor.apana.org.au>
Date: Tue, 12 Sep 2023 12:02:11 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Gatien Chevallier <gatien.chevallier@...s.st.com>
Cc: Olivia Mackall <olivia@...enic.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
Lionel Debieve <lionel.debieve@...s.st.com>,
linux-crypto@...r.kernel.org, devicetree@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 05/10] hwrng: stm32 - rework error handling in
stm32_rng_read()
On Fri, Sep 08, 2023 at 06:51:15PM +0200, Gatien Chevallier wrote:
>
> + if (WARN_ON(sr & RNG_SR_CEIS), "RNG clock too slow - %x\n", sr)
Introducing an unconditional WARN_ON is not acceptable. If you
really need it, make it WARN_ON_ONCE. But why does this need
to be a WARN instead of dev_err?
Cheers,
--
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Powered by blists - more mailing lists