[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171005033925.GA31996@gondor.apana.org.au>
Date: Thu, 5 Oct 2017 11:39:25 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Fabien DESSENNE <fabien.dessenne@...com>
Cc: "David S . Miller" <davem@...emloft.net>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Alexandre TORGUE <alexandre.torgue@...com>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Benjamin GAIGNARD <benjamin.gaignard@...com>,
Lionel DEBIEVE <lionel.debieve@...com>,
Ludovic BARRE <ludovic.barre@...com>,
Corentin Labbe <clabbe.montjoie@...il.com>
Subject: Re: [PATCH v3 1/3] crypto: engine - permit to enqueue aead_request
On Tue, Oct 03, 2017 at 07:48:08AM +0000, Fabien DESSENNE wrote:
>
> It looks like there is no more activity around this "crypto_engine
> interface clean up" task.
> This unfortunately has been blocking the introduction of this new STM32
> crypto driver for 3 months now.
> Would it make sense to have this driver reviewed first, and then
> reworked (I expect minor update here) when the interface update is ready?
Hmm, is it possible to disable the AEAD part of the driver first?
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