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: OMAP: miscellaneous PRCM and hwmod updates for v3.12
Date: Mon, 26 Aug 2013 04:17:08 -0700 [thread overview]
Message-ID: <20130826111708.GD7656@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1308231932400.22768@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [130823 12:40]:
> Hi Tony
>
> The following changes since commit b36f4be3de1b123d8601de062e7dbfc904f305fb:
>
> Linux 3.11-rc6 (2013-08-18 14:36:53 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git tags/for-v3.12/omap-prcm-hwmod
>
> for you to fetch changes up to 4514b4d7fcad2a84066c73966c6a7823ea1b3749:
>
> Merge branches 'hwmod_devel_v3.12', 'prcm_devel_v3.12' and 'am33xx_devel_v3.12' into prcm_a_for_v3.12 (2013-08-23 12:49:48 -0600)
>
> ----------------------------------------------------------------
>
> Various OMAP PRCM & hwmod fixes and improvements. Notable changes
> include:
>
> - a fix for OMAP4 PLL locking to avoid a bootloader dependency that
> causes nasty log spew on startup
>
> - AM33xx DEBUGSS support fixes in hwmod data
>
> - OMAP5 mailbox support in hwmod data
>
> Basic test logs are here:
>
> http://www.pwsan.com/omap/testlogs/prcm_a_for_v3.12/20130823125002/
>
> Note that the 3530 failure is due to the mysterious transient serial
> issue affecting 3530 for several releases now, which causes a log
> parsing failure. PM still seems to work.
Thanks pulling into omap-for-v3.12/prcm.
Regards,
Tony
prev parent reply other threads:[~2013-08-26 11:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 19:33 [GIT PULL] ARM: OMAP: miscellaneous PRCM and hwmod updates for v3.12 Paul Walmsley
2013-08-26 11:17 ` 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=20130826111708.GD7656@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).