linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gilad Ben-Yossef <gilad@benyossef.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>
Cc: Ofir Drang <ofir.drang@arm.com>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] crypto: ccree - fixes
Date: Wed, 29 Jan 2020 16:37:53 +0200	[thread overview]
Message-ID: <20200129143757.680-1-gilad@benyossef.com> (raw)

Fixes in AEAD DMA mapping code and blocksize reporting

Gilad Ben-Yossef (4):
  crypto: ccree - protect against empty or NULL scatterlists
  crypto: ccree - only try to map auth tag if needed
  crypto: ccree - fix some reported cipher block sizes
  crypto: ccree - fix AEAD blocksize registration

 drivers/crypto/ccree/cc_aead.c       |  1 +
 drivers/crypto/ccree/cc_buffer_mgr.c | 68 +++++++++++++---------------
 drivers/crypto/ccree/cc_buffer_mgr.h |  1 +
 drivers/crypto/ccree/cc_cipher.c     |  8 +++-
 4 files changed, 39 insertions(+), 39 deletions(-)

-- 
2.25.0


             reply	other threads:[~2020-01-29 14:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-29 14:37 Gilad Ben-Yossef [this message]
2020-01-29 14:37 ` [PATCH 1/4] crypto: ccree - protect against empty or NULL scatterlists Gilad Ben-Yossef
2020-01-29 14:37 ` [PATCH 2/4] crypto: ccree - only try to map auth tag if needed Gilad Ben-Yossef
2020-01-29 14:37 ` [PATCH 3/4] crypto: ccree - fix some reported cipher block sizes Gilad Ben-Yossef
2020-01-29 14:57   ` Geert Uytterhoeven
2020-01-29 14:37 ` [PATCH 4/4] crypto: ccree - fix AEAD blocksize registration Gilad Ben-Yossef
2020-01-29 15:17   ` Geert Uytterhoeven
2020-01-30 11:33     ` Gilad Ben-Yossef
2020-01-30 13:19       ` Geert Uytterhoeven
2020-02-02 15:32         ` Gilad Ben-Yossef
2020-02-02 16:21           ` Gilad Ben-Yossef
2020-02-13  9:19 ` [PATCH 0/4] crypto: ccree - fixes 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=20200129143757.680-1-gilad@benyossef.com \
    --to=gilad@benyossef.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ofir.drang@arm.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;
as well as URLs for NNTP newsgroup(s).