From: "Mark A. Greer" <mgreer@animalcreek.com>
To: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au,
davem@davemloft.net, dmitry.kasatkin@intel.com,
rmk+kernel@arm.linux.org.uk, paul@pwsan.com,
khilman@deeprootsystems.com
Subject: Re: [PATCH 0/7] crypto: omap-aes updates
Date: Mon, 19 Nov 2012 15:45:19 -0700 [thread overview]
Message-ID: <20121119224519.GA7349@animalcreek.com> (raw)
In-Reply-To: <1353351832-6685-1-git-send-email-mgreer@animalcreek.com>
On Mon, Nov 19, 2012 at 12:03:45PM -0700, Mark A. Greer wrote:
> From: "Mark A. Greer" <mgreer@animalcreek.com>
>
> This series updates the crypto omap-aes driver and supporting
> infrastructure.
>
> Notes:
>
> a) Based on omap-sham patches recently submitted, XXX
^^^
That was supposed to say that the series is based on the recently
submitted omap-sham updates:
http://permalink.gmane.org/gmane.linux.ports.arm.omap/89689
next prev parent reply other threads:[~2012-11-19 22:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 19:03 [PATCH 0/7] crypto: omap-aes updates Mark A. Greer
2012-11-19 19:03 ` [PATCH 1/7] ARM: OMAP2xxx: hwmod: Convert AES crypto devcie data to hwmod Mark A. Greer
2012-11-19 19:03 ` [PATCH 2/7] ARM: OMAP3xxx: hwmod: Convert AES crypto device " Mark A. Greer
2012-11-19 19:03 ` [PATCH 3/7] ARM: OMAP2+: Remove unnecessary message when no AES IP is present Mark A. Greer
2012-11-19 19:03 ` [PATCH 4/7] crypto: omap-aes: Remove cpu_is/omap_type check from driver Mark A. Greer
2012-11-21 1:03 ` Tony Lindgren
2012-11-19 19:03 ` [PATCH 5/7] crypto: omap-aes: Convert to use pm_runtime API Mark A. Greer
2012-11-19 19:03 ` [PATCH 6/7] crypto: omap-aes: Add code to use dmaengine API Mark A. Greer
2012-11-19 19:03 ` [PATCH 7/7] crypto: omap-aes: Remove usage of private DMA API Mark A. Greer
2012-11-19 22:45 ` Mark A. Greer [this message]
2012-11-20 12:08 ` [PATCH 0/7] crypto: omap-aes updates Kasatkin, Dmitry
2012-12-05 10:28 ` Kasatkin, Dmitry
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=20121119224519.GA7349@animalcreek.com \
--to=mgreer@animalcreek.com \
--cc=davem@davemloft.net \
--cc=dmitry.kasatkin@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rmk+kernel@arm.linux.org.uk \
/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