Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752430AbdLGJhN (ORCPT ); Thu, 7 Dec 2017 04:37:13 -0500 Received: from mail-wm0-f68.google.com ([74.125.82.68]:43629 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752365AbdLGJhJ (ORCPT ); Thu, 7 Dec 2017 04:37:09 -0500 X-Google-Smtp-Source: AGs4zMZ5Fw1p0vsrGwsZjS3/ERy56F4G272LE9T1W4sDfsTvAm6LPV7q87joBa0eoiYsOu2j+9/ujA== Date: Thu, 7 Dec 2017 10:37:05 +0100 From: Corentin Labbe To: Fabien DESSENNE Cc: "herbert@gondor.apana.org.au" , Alexandre TORGUE , "arei.gonglei@huawei.com" , "davem@davemloft.net" , "jasowang@redhat.com" , "mcoquelin.stm32@gmail.com" , "mst@redhat.com" , Lionel DEBIEVE , Benjamin GAIGNARD , "linux-arm-kernel@lists.infradead.org" , "linux-crypto@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "virtualization@lists.linux-foundation.org" Subject: Re: [PATCH RFC 0/4] crypto: engine - Permit to enqueue all async requests Message-ID: <20171207093705.GB21647@Red> References: <20171129084121.9385-1-clabbe.montjoie@gmail.com> <4d58a1fc-8577-3fdb-ae6b-e1fade7c6582@st.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4d58a1fc-8577-3fdb-ae6b-e1fade7c6582@st.com> User-Agent: Mutt/1.7.2 (2016-11-26) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 978 Lines: 30 On Wed, Dec 06, 2017 at 10:59:47AM +0000, Fabien DESSENNE wrote: > Hi Corentin, > > > I am fine with this proposal: it is generic enough and I have been able > to test and run the crypto engine with aead_request without changing any > single line of code. > > This is what I need to be able to send the AEAD extension of the > stm32-cryp driver (successfully tested with your engine upgrade proposal). > > > I have also tested the stm32-hash patch. > > Note that stm32-cryp (new driver applied by Herbert recently > [https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git/commit/?id=9e054ec21ef8344345b28603fb272fe999f735db]) > would also need to be converted to the new crypto engine API : this is a > trivial patch. Yes, patch for converting it is already done. > > Thank you for your proposal, I hope that this proposal is fine for > Herbert too. > Thanks for your test, I hope other maintainer will test it also. Regards Corentin Labbe