From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] ARM: OMAP2+: hwmod changes for v3.13
Date: Fri, 11 Oct 2013 15:26:34 -0700 [thread overview]
Message-ID: <20131011222634.GB29913@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1310111659500.27397@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan•com> [131011 10:08]:
> Hi Tony,
>
> The following changes since commit d0e639c9e06d44e713170031fe05fb60ebe680af:
>
> Linux 3.12-rc4 (2013-10-06 14:00:20 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git tags/for-v3.13/hwmod
>
> for you to fetch changes up to ace1e3ec4a2540c783e65884bb7be9cd45a0a295:
>
> ARM: AM33xx: hwmod: Add RNG module data (2013-10-09 09:02:51 -0600)
>
> ----------------------------------------------------------------
> Some OMAP hwmod changes for 3.13. Significant changes here include:
>
> - support for moving some of the hwmod flags to DT data
>
> - support for the SSI, hardware spinlock, USB host/TLL, and RNG IP
> blocks for various OMAPs
>
> - a fix that again decouples hwmod data changes from unrelated DT data
> patchsets
>
> Basic test logs are available at:
>
> http://www.pwsan.com/omap/testlogs/prcm_fixes_v3.13/20131009094936/
>
> The summary reports that the 4460varsomom boots are failing, but this looks
> incorrect - it's probably a bug in the validation scripts here.
OK I'll do a test on my panda es before sending out the branches
and will apply that one hwmod patch Benoit had queued on top
of this. So pulling into omap-for-v3.13/hwmod.
Regards,
Tony
next prev parent reply other threads:[~2013-10-11 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 17:00 [GIT PULL] ARM: OMAP2+: hwmod changes for v3.13 Paul Walmsley
2013-10-11 22:26 ` Tony Lindgren [this message]
2013-10-11 22:30 ` Paul Walmsley
2013-10-11 22:37 ` Tony Lindgren
2013-10-12 10:18 ` Afzal Mohammed
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=20131011222634.GB29913@atomide.com \
--to=tony@atomide$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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