linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sivaprakash Murugesan <sivaprak@codeaurora.org>
To: herbert@gondor.apana.org.au, davem@davemloft.net,
	stanimir.varbanov@linaro.org, ardb@kernel.org,
	sivaprak@codeaurora.org, cotequeiroz@gmail.com,
	ebiggers@google.com, horia.geanta@nxp.com,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] qce crypto fixes for tcrypto failures
Date: Mon, 22 Jun 2020 11:45:03 +0530	[thread overview]
Message-ID: <1592806506-23978-1-git-send-email-sivaprak@codeaurora.org> (raw)

while running tcrypto test cases on qce crypto engine few failures are
noticed, this is mainly because of the updates on tcrypto driver and
not testing qce reqgularly with mainline tcrypto driver.

This series tries to address few of the errors while running tcrypto on
qce.

Sivaprakash Murugesan (3):
  crypto: qce: support zero length test vectors
  crypto: qce: re-initialize context on import
  crypto: qce: sha: Do not modify scatterlist passed along with request

 drivers/crypto/Kconfig      |  2 ++
 drivers/crypto/qce/common.h |  2 ++
 drivers/crypto/qce/sha.c    | 36 +++++++++++++++++++++++++++++-------
 3 files changed, 33 insertions(+), 7 deletions(-)

-- 
2.7.4


             reply	other threads:[~2020-06-22  6:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22  6:15 Sivaprakash Murugesan [this message]
2020-06-22  6:15 ` [PATCH 1/3] crypto: qce: support zero length test vectors Sivaprakash Murugesan
2020-06-22  6:15 ` [PATCH 2/3] crypto: qce: re-initialize context on import Sivaprakash Murugesan
2020-06-22  6:15 ` [PATCH 3/3] crypto: qce: sha: Do not modify scatterlist passed along with request Sivaprakash Murugesan
2020-07-03  4:48 ` [PATCH 0/3] qce crypto fixes for tcrypto failures Herbert Xu

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=1592806506-23978-1-git-send-email-sivaprak@codeaurora.org \
    --to=sivaprak@codeaurora.org \
    --cc=ardb@kernel.org \
    --cc=cotequeiroz@gmail.com \
    --cc=davem@davemloft.net \
    --cc=ebiggers@google.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=horia.geanta@nxp.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stanimir.varbanov@linaro.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;
as well as URLs for NNTP newsgroup(s).