From: Dmitry Kasatkin <dmitry.kasatkin@nokia.com>
To: herbert@gondor.hengli.com.au
Cc: linux-crypto@vger.kernel.org, linux-omap@vger.kernel.org
Subject: [PATCH v3 0/8] omap-sham: OMAP SHA1/MD5 driver fixes and improvements
Date: Fri, 19 Nov 2010 16:04:21 +0200 [thread overview]
Message-ID: <cover.1290174993.git.dmitry.kasatkin@nokia.com> (raw)
Hi,
Here is a set of patches which provides fixes and improvements.
Based on Herbert feedback it also includes fixes so that calling final()
is not mandatory.
BR, Dmitry
Dmitry Kasatkin (8):
omap-sham: uses digest buffer in request context
omap-sham: DMA initialization fixes for off mode
omap-sham: error handling improved
omap-sham: removed redundunt locking
omap-sham: crypto_ahash_final() now not need to be called.
omap-sham: hash-in-progress is stored in hw format
omap-sham: FLAGS_FIRST is redundant and removed
omap-sham: zero-copy scatterlist handling
drivers/crypto/omap-sham.c | 379 +++++++++++++++++++++++++-------------------
1 files changed, 218 insertions(+), 161 deletions(-)
next reply other threads:[~2010-11-19 14:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 14:04 Dmitry Kasatkin [this message]
2010-11-19 14:04 ` [PATCH v3 1/8] omap-sham: uses digest buffer in request context Dmitry Kasatkin
2010-11-19 14:04 ` [PATCH v3 2/8] omap-sham: DMA initialization fixes for off mode Dmitry Kasatkin
2010-11-19 14:04 ` [PATCH v3 3/8] omap-sham: error handling improved Dmitry Kasatkin
2010-11-19 14:04 ` [PATCH v3 4/8] omap-sham: removed redundunt locking Dmitry Kasatkin
2010-11-19 14:04 ` [PATCH v3 5/8] omap-sham: crypto_ahash_final() now not need to be called Dmitry Kasatkin
2010-11-19 14:04 ` [PATCH v3 6/8] omap-sham: hash-in-progress is stored in hw format Dmitry Kasatkin
2010-11-19 14:04 ` [PATCH v3 7/8] omap-sham: FLAGS_FIRST is redundant and removed Dmitry Kasatkin
2010-11-19 14:04 ` [PATCH v3 8/8] omap-sham: zero-copy scatterlist handling Dmitry Kasatkin
2010-11-27 8:39 ` [PATCH v3 0/8] omap-sham: OMAP SHA1/MD5 driver fixes and improvements Herbert Xu
2010-11-30 7:40 ` Dmitry Kasatkin
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=cover.1290174993.git.dmitry.kasatkin@nokia.com \
--to=dmitry.kasatkin@nokia.com \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-omap@vger.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;
as well as URLs for NNTP newsgroup(s).