[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <78ad6a62-190c-e4fe-dd23-e1d058f9bbb2@nexus-software.ie>
Date: Fri, 2 Feb 2018 11:20:56 +0000
From: Bryan O'Donoghue <pure.logic@...us-software.ie>
To: Horia Geantă <horia.geanta@....com>,
Aymen Sghaier <aymen.sghaier@....com>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc: Fabio Estevam <fabio.estevam@....com>, Peng Fan <peng.fan@....com>,
"davem@...emloft.net" <davem@...emloft.net>,
"lukas.auer@...ec.fraunhofer.de" <lukas.auer@...ec.fraunhofer.de>,
"rui.silva@...aro.org" <rui.silva@...aro.org>,
"ryan.harkin@...aro.org" <ryan.harkin@...aro.org>,
Herbert Xu <herbert@...dor.apana.org.au>
Subject: Re: [PATCH v3 2/5] crypto: caam: Fix endless loop when RNG is already
initialized
On 01/02/18 12:16, Horia Geantă wrote:
> If the loop cannot exit based on value of "ret" != -EAGAIN, then it means
> caam_probe() will eventually fail due to ret == -EAGAIN:
> if (ret) {
> dev_err(dev, "failed to instantiate RNG");
> goto caam_remove;
> }
For me it's an endless loop applying the first two
https://patchwork.ozlabs.org/patch/866460/
https://patchwork.ozlabs.org/patch/866462/
but not this one
https://patchwork.ozlabs.org/patch/865890/
> Please provide more details, so that the root cause is found and fixed.
np
---
bod
Powered by blists - more mailing lists