From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] ARM: OMAP2+: standardize integration for AES & SHA/MD5 IP blocks for 3.10
Date: Mon, 1 Apr 2013 10:08:12 -0700 [thread overview]
Message-ID: <20130401170811.GL10155@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1303302244540.6436@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [130330 15:51]:
> Hi Tony,
>
> The following changes since commit 78e52e026d288aad88b46bff0d94b05e145c4583:
>
> ARM: OMAP2+: clock data: Remove CK_* flags (2013-03-18 09:57:39 -0600)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git tags/omap-devel-a-for-3.10
>
> for you to fetch changes up to 1cb804b93f506dfba5fd684a8ea63706aaa8e709:
>
> ARM: AM33XX: hwmod: Update and uncomment AES0 module data (2013-03-30 15:52:17 -0600)
>
> ----------------------------------------------------------------
> For OMAP2+ SoCs, convert the SHA/MD5 and AES accelerator integration
> code and data to use hwmod and omap_device. This is a prerequisite for
> moving the hwmod code out of arch/arm.
>
> Basic test logs are available at:
>
> http://www.pwsan.com/omap/testlogs/sham_aes_integration_devel_3.10/20130330155313/
Thanks pulling into omap-for-v3.10/crypto.
Regards,
Tony
prev parent reply other threads:[~2013-04-01 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-30 22:47 [GIT PULL] ARM: OMAP2+: standardize integration for AES & SHA/MD5 IP blocks for 3.10 Paul Walmsley
2013-04-01 17:08 ` Tony Lindgren [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=20130401170811.GL10155@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
/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).