From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP2+: sparse & PRCM fixes for v3.8-rc1
Date: Tue, 1 Jan 2013 10:18:02 -0800 [thread overview]
Message-ID: <20130101181801.GC22106@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1212281835450.27761@utopia.booyaka.com>
Hi,
* Paul Walmsley <paul@pwsan.com> [121228 10:39]:
> Hi Tony
>
> The following changes since commit a49f0d1ea3ec94fc7cf33a7c36a16343b74bd565:
>
> Linux 3.8-rc1 (2012-12-21 17:19:00 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git tags/omap-fixes-a-for-v3.8-rc
>
> for you to fetch changes up to 0d541cf2b983758186c972479d4e9f916679dd7a:
>
> ARM: OMAP2/3: PRM: fix bogus OMAP2xxx powerstate return values (2012-12-28 02:10:44 -0700)
>
> ----------------------------------------------------------------
> Some OMAP PRCM and sparse fixes against v3.8-rc1. A basic set of test
> logs are available here:
>
> http://www.pwsan.com/omap/testlogs/prcm_fixes_b_3.8-rc/20121228032747/
>
> (The 3730 Beagle XM here has an intermittent failure mounting SD root,
> but the suspicion right now is that this is due to a failing SD card,
> rather than any change introduced by these patches.)
Sorry for the delay, just noted few issues with the counter_32k.h and
sram.h patches that just replied to. For the plat-omap code it's OK to
include <plat/*.h> for multiplatform builds. Other than that looks
good to me.
Regards,
Tony
next prev parent reply other threads:[~2013-01-01 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 18:37 [GIT PULL] ARM: OMAP2+: sparse & PRCM fixes for v3.8-rc1 Paul Walmsley
2013-01-01 18:18 ` Tony Lindgren [this message]
2013-01-02 19:38 ` Paul Walmsley
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=20130101181801.GC22106@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).