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 v2] ARM: OMAP2+: sparse & PRCM fixes for v3.8-rc1
Date: Thu, 3 Jan 2013 11:33:49 -0800 [thread overview]
Message-ID: <20130103193349.GG25633@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1301021931430.17366@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [130102 11:41]:
> 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-a2-for-v3.8-rc
>
> for you to fetch changes up to 7e7fff8254e318cede06a1a8c55b0d86dd4d8c5b:
>
> ARM: OMAP2/3: PRM: fix bogus OMAP2xxx powerstate return values (2013-01-02 12:07:16 -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/20130102120724/
>
> 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.
>
> This second version includes a few changes requested by Tony Lindgren.
Thanks pulling into omap-for-v3.8-rc2/fixes.
Tony
prev parent reply other threads:[~2013-01-03 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 19:38 [GIT PULL v2] ARM: OMAP2+: sparse & PRCM fixes for v3.8-rc1 Paul Walmsley
2013-01-03 19:33 ` 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=20130103193349.GG25633@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).