From: Fabien DESSENNE <fabien.dessenne@st.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S . Miller" <davem@davemloft.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre TORGUE <alexandre.torgue@st.com>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Benjamin GAIGNARD <benjamin.gaignard@st.com>,
Lionel DEBIEVE <lionel.debieve@st.com>,
Ludovic BARRE <ludovic.barre@st.com>,
Corentin Labbe <clabbe.montjoie@gmail.com>
Subject: Re: [PATCH v3 1/3] crypto: engine - permit to enqueue aead_request
Date: Fri, 6 Oct 2017 09:26:07 +0000 [thread overview]
Message-ID: <9d89727b-f3cb-3322-6513-962e9df63ca8@st.com> (raw)
In-Reply-To: <20171005033925.GA31996@gondor.apana.org.au>
OK, I will send an initial version without the AEAD part.
On 05/10/17 05:39, Herbert Xu wrote:
> 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,
next prev parent reply other threads:[~2017-10-06 9:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 9:19 [PATCH v3 0/3] STM32 CRYP crypto driver Fabien Dessenne
2017-08-18 9:19 ` [PATCH v3 1/3] crypto: engine - permit to enqueue aead_request Fabien Dessenne
2017-09-22 9:09 ` Herbert Xu
2017-10-03 7:48 ` Fabien DESSENNE
2017-10-05 3:39 ` Herbert Xu
2017-10-06 9:26 ` Fabien DESSENNE [this message]
2017-08-18 9:19 ` [PATCH v3 2/3] dt-bindings: Document STM32 CRYP bindings Fabien Dessenne
2017-08-18 9:19 ` [PATCH v3 3/3] crypto: stm32 - Support for STM32 CRYP crypto module Fabien Dessenne
2017-09-18 9:40 ` [PATCH v3 0/3] STM32 CRYP crypto driver Fabien DESSENNE
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=9d89727b-f3cb-3322-6513-962e9df63ca8@st.com \
--to=fabien.dessenne@st.com \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@st.com \
--cc=clabbe.montjoie@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--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=ludovic.barre@st.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®