From: Tony Lindgren <tony@atomide.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Dmitry Kasatkin <dmitry.kasatkin@nokia.com>,
linux-crypto@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCHv4 0/2] omap-sham: OMAP SHA1/MD5 driver
Date: Wed, 5 May 2010 11:38:50 -0700 [thread overview]
Message-ID: <20100505183849.GB29604@atomide.com> (raw)
In-Reply-To: <20100503031139.GA31376@gondor.apana.org.au>
* Herbert Xu <herbert@gondor.apana.org.au> [100502 20:07]:
> On Wed, Apr 28, 2010 at 05:18:05PM +0300, Dmitry Kasatkin wrote:
> > Changes to v4:
> > - concurrent requests support via queue
> > - hmac
> > - shash support removed
> >
> > Dmitry Kasatkin (2):
> > crypto: updates omap sham device related platform code
> > crypto: omap-sham - omap sha1 & md5 driver
>
> Both patches applied. Thanks for all your hard work Dmitry!
Just noticed that the first patch should be updated:
CONFIG_ARCH_OMAP2 instead of CONFIG_ARCH_OMAP24XX
CONFIG_ARCH_OMAP3 instead of CONFIG_ARCH_OMAP34XX
BTW, chances are that this part will conflict with other
omap patches. But if that happens, we can move it to
the omap for-next.
Regards,
Tony
next prev parent reply other threads:[~2010-05-05 18:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 14:18 [PATCHv4 0/2] omap-sham: OMAP SHA1/MD5 driver Dmitry Kasatkin
2010-04-28 14:18 ` [PATCH 1/2] crypto: updates omap sham device related platform code Dmitry Kasatkin
2010-04-28 14:18 ` [PATCH 2/2] crypto: omap-sham - omap sha1 & md5 driver Dmitry Kasatkin
2010-05-03 3:11 ` [PATCHv4 0/2] omap-sham: OMAP SHA1/MD5 driver Herbert Xu
2010-05-05 18:38 ` Tony Lindgren [this message]
2010-05-10 11: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=20100505183849.GB29604@atomide.com \
--to=tony@atomide.com \
--cc=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).