From: Herbert Xu <herbert@gondor.apana.org.au>
To: Lionel Debieve <lionel.Debieve@st.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
linux-crypto@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Benjamin Gaignard <benjamin.gaignard@st.com>,
Fabien Dessenne <fabien.dessenne@st.com>,
Ludovic Barre <ludovic.barre@st.com>
Subject: Re: [PATCH 0/3] crypto: stm32/hash: Correction to improve robustness
Date: Thu, 15 Feb 2018 23:51:34 +0800 [thread overview]
Message-ID: <20180215155133.GL7352@gondor.apana.org.au> (raw)
In-Reply-To: <20180129142811.13273-1-lionel.Debieve@st.com>
On Mon, Jan 29, 2018 at 03:28:08PM +0100, Lionel Debieve wrote:
> From: Lionel Debieve <lionel.debieve@st.com>
>
> Hi,
>
> This patch serie will improve global robustness for stm32-hash driver.
>
> Patch #1 is fixing dma-burst issue when configuration is not set.
> Patch #2 solves issue that occurs when irq append during final req processing.
> Patch #3 is fixing an issue that have been introduced while managing padding but
> breaking the padding length calculation by hardware to generate correct hash.
>
> Regards,
>
> Lionel Debieve (3):
> crypto: stm32/hash: avoid error if maxburst not defined
> crypto: stm32/hash: fix performance issues
> crypto: stm32/hash: rework padding length
All applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2018-02-15 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 14:28 Lionel Debieve
2018-01-29 14:28 ` [PATCH 1/3] crypto: stm32/hash: avoid error if maxburst not defined Lionel Debieve
2018-01-29 14:28 ` [PATCH 2/3] crypto: stm32/hash: fix performance issues Lionel Debieve
2018-01-29 14:28 ` [PATCH 3/3] crypto: stm32/hash: rework padding length Lionel Debieve
2018-02-15 15:51 ` Herbert Xu [this message]
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=20180215155133.GL7352@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@st.com \
--cc=davem@davemloft.net \
--cc=fabien.dessenne@st.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=ludovic.barre@st.com \
--cc=mcoquelin.stm32@gmail.com \
/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®