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+: hwmod code and data changes for v4.2
Date: Tue, 2 Jun 2015 07:54:14 -0700 [thread overview]
Message-ID: <20150602145413.GK30984@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1506020321510.14902@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [150601 20:24]:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Tony,
>
> The following changes since commit e26081808edadfd257c6c9d81014e3b25e9a6118:
>
> Linux 4.1-rc4 (2015-05-18 10:13:47 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git tags/for-v4.2/omap-hwmod-a
>
> for you to fetch changes up to a55a744582e0dc106537ba5e508c340c39cfe454:
>
> ARM: OMAP3: Fix crypto support for HS devices (2015-06-01 19:23:04 -0600)
>
> The branch contains a AM43xx hwmod data change, and thus is based on
> v4.1-rc4 to avoid merge conflicts.
>
> - ----------------------------------------------------------------
> ARM: OMAP2+: hwmod code and data changes for v4.2
>
> Several OMAP2+ hwmod changes for v4.2. One patch cleans up a nasty
> interaction between the OMAP GPMC and the hwmod code when debugging is
> enabled. IP block integration data has been added for the AM43xx EMIF
> RAM controller. There's also a fix for the omap-aes driver when used in
> QEMU. And finally, some changes to the OMAP3 hwmod code to support the
> use of the security IP blocks (AES and SHA) on GP devices, or when they've
> specifically been enabled in the DT data.
>
> Basic build, boot, and power management test results are here:
>
> http://www.pwsan.com/omap/testlogs/omap-hwmod-a-for-v4.2/20150601192349/
Thanks pulling into omap-for-v4.2/soc.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP2+: hwmod code and data changes for v4.2
Date: Tue, 2 Jun 2015 07:54:14 -0700 [thread overview]
Message-ID: <20150602145413.GK30984@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1506020321510.14902@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [150601 20:24]:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Tony,
>
> The following changes since commit e26081808edadfd257c6c9d81014e3b25e9a6118:
>
> Linux 4.1-rc4 (2015-05-18 10:13:47 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git tags/for-v4.2/omap-hwmod-a
>
> for you to fetch changes up to a55a744582e0dc106537ba5e508c340c39cfe454:
>
> ARM: OMAP3: Fix crypto support for HS devices (2015-06-01 19:23:04 -0600)
>
> The branch contains a AM43xx hwmod data change, and thus is based on
> v4.1-rc4 to avoid merge conflicts.
>
> - ----------------------------------------------------------------
> ARM: OMAP2+: hwmod code and data changes for v4.2
>
> Several OMAP2+ hwmod changes for v4.2. One patch cleans up a nasty
> interaction between the OMAP GPMC and the hwmod code when debugging is
> enabled. IP block integration data has been added for the AM43xx EMIF
> RAM controller. There's also a fix for the omap-aes driver when used in
> QEMU. And finally, some changes to the OMAP3 hwmod code to support the
> use of the security IP blocks (AES and SHA) on GP devices, or when they've
> specifically been enabled in the DT data.
>
> Basic build, boot, and power management test results are here:
>
> http://www.pwsan.com/omap/testlogs/omap-hwmod-a-for-v4.2/20150601192349/
Thanks pulling into omap-for-v4.2/soc.
Tony
next prev parent reply other threads:[~2015-06-02 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 3:22 [GIT PULL] ARM: OMAP2+: hwmod code and data changes for v4.2 Paul Walmsley
2015-06-02 3:22 ` Paul Walmsley
2015-06-02 14:54 ` Tony Lindgren [this message]
2015-06-02 14:54 ` Tony Lindgren
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=20150602145413.GK30984@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.