From: Dmitry Kasatkin <dmitry.kasatkin@nokia.com>
To: ext Herbert Xu <herbert@gondor.hengli.com.au>
Cc: <linux-crypto@vger.kernel.org>, <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 0/4] crypto: omap-sham driver fixes
Date: Tue, 26 Apr 2011 10:18:17 +0300 [thread overview]
Message-ID: <4DB671B9.5070003@nokia.com> (raw)
In-Reply-To: <20110426063652.GB19539@gondor.apana.org.au>
Thanks.
On 26/04/11 09:36, ext Herbert Xu wrote:
> On Wed, Apr 20, 2011 at 01:34:54PM +0300, Dmitry Kasatkin wrote:
>> Hi,
>>
>> Here is few patches with couple of important fixes...
> All applied. Thanks!
prev parent reply other threads:[~2011-04-26 7:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 10:34 [PATCH 0/4] crypto: omap-sham driver fixes Dmitry Kasatkin
2011-04-20 10:34 ` [PATCH 1/4] crypto: omap-sham - fix concurrent sha1 calculations Dmitry Kasatkin
2011-04-20 10:34 ` [PATCH 2/4] crypto: omap-sham - remove debug print Dmitry Kasatkin
2011-04-20 10:34 ` [PATCH 3/4] crypto: omap-sham - enable driver for EMU chips Dmitry Kasatkin
2011-04-20 10:34 ` [PATCH 4/4] crypto: omap-sham - hmac calculation bug fix for sha1 base hash Dmitry Kasatkin
2011-04-26 6:36 ` [PATCH 0/4] crypto: omap-sham driver fixes Herbert Xu
2011-04-26 7:18 ` Dmitry Kasatkin [this message]
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=4DB671B9.5070003@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).