linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Kasatkin <dmitry.kasatkin@nokia.com>
To: herbert@gondor.apana.org.au
Cc: linux-crypto@vger.kernel.org, linux-omap@vger.kernel.org
Subject: [PATCH 0/2] crypto: omap-sha1-md5: OMAP3 SHA1 & MD5 driver
Date: Wed, 17 Mar 2010 15:12:49 +0200	[thread overview]
Message-ID: <cover.1268830685.git.dmitry.kasatkin@nokia.com> (raw)

Earlier kernel contained omap sha1 and md5 driver, which was not maintained,
was not ported to new crypto APIs and removed from the source tree.

This driver implements async and sync crypto API.

It still contains pr_debug() for debugging purpose.
Will be remove for integration.

Dmitry Kasatkin (2):
  sec: omap sha1 & md5 driver
  sec: Makefile/Kconfig update for omap sha1 md5 driver

 drivers/crypto/Kconfig         |    9 +
 drivers/crypto/Makefile        |    2 +
 drivers/crypto/omap-sha1-md5.c | 1449 ++++++++++++++++++++++++++++++++++++++++
 3 files changed, 1460 insertions(+), 0 deletions(-)
 create mode 100644 drivers/crypto/omap-sha1-md5.c


             reply	other threads:[~2010-03-17 13:12 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17 13:12 Dmitry Kasatkin [this message]
2010-03-17 13:12 ` [PATCH 1/2] sec: omap sha1 & md5 driver Dmitry Kasatkin
2010-03-17 17:08   ` Felipe Balbi
2010-03-17 20:49     ` Tony Lindgren
2010-03-17 13:12 ` [PATCH 2/2] sec: Makefile/Kconfig update for omap sha1 " Dmitry Kasatkin
2010-03-23 11:32 ` [PATCH 0/2] crypto: omap-sha1-md5: OMAP3 SHA1 & MD5 driver Herbert Xu
2010-03-24  7:31   ` Dmitry Kasatkin
2010-03-24 14:51   ` Dmitry Kasatkin
2010-04-08 14:07     ` Herbert Xu
2010-04-08 14:04   ` Herbert Xu
  -- strict thread matches above, loose matches on Subject: below --
2010-04-08 16:35 Dmitry.Kasatkin
2010-04-13  8:59 ` Herbert Xu
2010-04-13  9:39   ` Dmitry Kasatkin
2010-04-13 10:03     ` Herbert Xu
2010-04-13 10:13       ` Dmitry Kasatkin
2010-04-13 12:02         ` Herbert Xu
2010-04-13 13:00           ` Dmitry Kasatkin
2010-04-13 14:45             ` Herbert Xu
2010-04-13 15:16               ` Uri Simchoni
2010-04-13 15:21                 ` Dmitry Kasatkin
2010-04-14  0:44                   ` Herbert Xu
2010-04-14  6:37                     ` Dmitry Kasatkin
2010-04-14  6:44                       ` Herbert Xu
2010-04-14  6:51                         ` Dmitry Kasatkin
2010-04-14  6:55                           ` Herbert Xu
2010-04-16  7:44                             ` Dmitry Kasatkin
2010-04-19 13:27                               ` Herbert Xu
2010-04-13 10:15       ` Dmitry Kasatkin
2010-04-13 12:00         ` Uri Simchoni
2010-04-13 12:10         ` Herbert Xu
2010-04-13 13:44           ` Dmitry Kasatkin
2010-04-13 14:36             ` Dmitry Kasatkin
2010-04-13 14:42               ` Herbert Xu
2010-04-13 15:33                 ` Dmitry Kasatkin
2010-04-14  0:47                   ` Herbert Xu
2010-04-13 14:48             ` Herbert Xu
2010-04-13 15:48               ` Dmitry Kasatkin
2010-04-14  0:50                 ` 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=cover.1268830685.git.dmitry.kasatkin@nokia.com \
    --to=dmitry.kasatkin@nokia.com \
    --cc=herbert@gondor.apana.org.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).