From: Ben Hutchings <ben.hutchings@mind.be>
To: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: linux-crypto@vger.kernel.org, linux-omap@vger.kernel.org,
Lokesh Vutla <lokeshvutla@ti.com>,
Tero Kristo <kristo@kernel.org>
Subject: [PATCH 0/2] omap-crypto fixes
Date: Wed, 11 Aug 2021 02:03:33 +0200 [thread overview]
Message-ID: <20210811000333.GA22095@cephalopod> (raw)
These are two non-urgent fixes for the omap-crypto drivers.
Ben.
Ben Hutchings (2):
crypto: omap - Avoid redundant copy when using truncated sg list
crypto: omap - Fix inconsistent locking of device lists
drivers/crypto/omap-aes.c | 8 ++++----
drivers/crypto/omap-crypto.c | 2 +-
drivers/crypto/omap-des.c | 8 ++++----
drivers/crypto/omap-sham.c | 12 ++++++------
4 files changed, 15 insertions(+), 15 deletions(-)
--
2.20.1
next reply other threads:[~2021-08-11 0:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 0:03 Ben Hutchings [this message]
2021-08-11 0:05 ` [PATCH 1/2] crypto: omap - Avoid redundant copy when using truncated sg list Ben Hutchings
2021-08-11 0:06 ` [PATCH 2/2] crypto: omap - Fix inconsistent locking of device lists Ben Hutchings
2021-08-21 7:49 ` [PATCH 0/2] omap-crypto 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=20210811000333.GA22095@cephalopod \
--to=ben.hutchings@mind.be \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kristo@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.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