All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: Fabien DESSENNE <fabien.dessenne@st.com>
Cc: "herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
	Alexandre TORGUE <alexandre.torgue@st.com>,
	"arei.gonglei@huawei.com" <arei.gonglei@huawei.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"jasowang@redhat.com" <jasowang@redhat.com>,
	"mcoquelin.stm32@gmail.com" <mcoquelin.stm32@gmail.com>,
	"mst@redhat.com" <mst@redhat.com>,
	Lionel DEBIEVE <lionel.debieve@st.com>,
	Benjamin GAIGNARD <benjamin.gaignard@st.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"virtualization@lists.linux-foundation.org"
	<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH RFC 0/4] crypto: engine - Permit to enqueue all async requests
Date: Thu, 7 Dec 2017 10:37:05 +0100	[thread overview]
Message-ID: <20171207093705.GB21647@Red> (raw)
In-Reply-To: <4d58a1fc-8577-3fdb-ae6b-e1fade7c6582@st.com>

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

WARNING: multiple messages have this Message-ID (diff)
From: clabbe.montjoie@gmail.com (Corentin Labbe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 0/4] crypto: engine - Permit to enqueue all async requests
Date: Thu, 7 Dec 2017 10:37:05 +0100	[thread overview]
Message-ID: <20171207093705.GB21647@Red> (raw)
In-Reply-To: <4d58a1fc-8577-3fdb-ae6b-e1fade7c6582@st.com>

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

  parent reply	other threads:[~2017-12-07  9:37 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29  8:41 [PATCH RFC 0/4] crypto: engine - Permit to enqueue all async requests Corentin Labbe
2017-11-29  8:41 ` Corentin Labbe
2017-11-29  8:41 ` [PATCH RFC 1/4] " Corentin Labbe
2017-11-29  8:41   ` Corentin Labbe
2017-11-29  8:41   ` Corentin Labbe
2017-12-06 11:02   ` Fabien DESSENNE
2017-12-06 11:02     ` Fabien DESSENNE
2017-12-07  9:24     ` Corentin Labbe
2017-12-07  9:24       ` Corentin Labbe
2017-12-07  9:24       ` Corentin Labbe
2017-12-06 11:02   ` Fabien DESSENNE
2017-12-22  6:57   ` Herbert Xu
2017-12-22  6:57   ` Herbert Xu
2017-12-22  6:57     ` Herbert Xu
2017-12-22  8:41     ` Corentin Labbe
2017-12-22  8:41     ` Corentin Labbe
2017-12-22  8:41       ` Corentin Labbe
2017-12-22  9:06       ` Herbert Xu
2017-12-22  9:06         ` Herbert Xu
2017-12-22  9:06         ` Herbert Xu
2017-12-22  9:34         ` Corentin Labbe
2017-12-22  9:34           ` Corentin Labbe
2017-12-22  9:34           ` Corentin Labbe
2017-11-29  8:41 ` Corentin Labbe
2017-11-29  8:41 ` [PATCH RFC 2/4] crypto: omap: convert to new crypto engine API Corentin Labbe
2017-11-29  8:41   ` Corentin Labbe
2017-11-29  8:41   ` Corentin Labbe
2017-11-29  8:41 ` [PATCH RFC 3/4] crypto: virtio: " Corentin Labbe
2017-11-29  8:41 ` Corentin Labbe
2017-11-29  8:41   ` Corentin Labbe
2017-11-29  8:41 ` [PATCH RFC 4/4] crypto: stm32: convert to the " Corentin Labbe
2017-11-29  8:41 ` Corentin Labbe
2017-11-29  8:41   ` Corentin Labbe
2017-12-06 11:03   ` Fabien DESSENNE
2017-12-06 11:03     ` Fabien DESSENNE
2017-12-06 11:03   ` Fabien DESSENNE
2017-12-06 10:59 ` [PATCH RFC 0/4] crypto: engine - Permit to enqueue all async requests Fabien DESSENNE
2017-12-06 10:59 ` Fabien DESSENNE
2017-12-06 10:59   ` Fabien DESSENNE
2017-12-07  9:37   ` Corentin Labbe
2017-12-07  9:37   ` Corentin Labbe [this message]
2017-12-07  9:37     ` Corentin Labbe
  -- strict thread matches above, loose matches on Subject: below --
2017-11-29  8:41 Corentin Labbe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171207093705.GB21647@Red \
    --to=clabbe.montjoie@gmail.com \
    --cc=alexandre.torgue@st.com \
    --cc=arei.gonglei@huawei.com \
    --cc=benjamin.gaignard@st.com \
    --cc=davem@davemloft.net \
    --cc=fabien.dessenne@st.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=jasowang@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lionel.debieve@st.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.