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+: first set of PRM/CM cleanups for 3.8
Date: Wed, 24 Oct 2012 17:03:35 -0700 [thread overview]
Message-ID: <20121025000334.GF11928@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1210211912410.26128@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [121021 12:15]:
> Hi Tony
>
> The following changes since commit 6f0c0580b70c89094b3422ba81118c7b959c7556:
>
> Linux 3.7-rc2 (2012-10-20 12:11:32 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git tags/omap-cleanup-a-for-3.8
>
> for you to fetch changes up to 2bb2a5d30abb0dc99d074877bfad2056142c730b:
>
> ARM: OMAP2+: PRM: create PRM reset source API for the watchdog timer driver (2012-10-21 01:01:13 -0600)
>
> ----------------------------------------------------------------
> The first set of OMAP PRM/CM-related cleanup patches for 3.8.
> Prepares for the future move of the PRM/CM code to drivers/. Also
> includes some prcm.[ch] cleanup patches from the WDTIMER cleanup
> series that don't need external acks.
>
> Basic test logs for this branch on top of v3.7-rc2 are here:
>
> http://www.pwsan.com/omap/testlogs/prcm_cleanup_a_3.8/20121021123719/
>
> But due to the number of unrelated regressions present in v3.7-rc[12],
> it's not particularly usable as a testing base. With reverts, fixes,
> and workarounds applied as documented in:
>
> http://www.pwsan.com/omap/testlogs/test_v3.7-rc2/20121020134755/README.txt
>
> the following test logs were obtained:
>
> http://www.pwsan.com/omap/testlogs/prcm_cleanup_a_3.8/20121020231757/
>
> which indicate that the series tests cleanly.
Thanks pulling into omap-for-v3.8/cleanup-prcm.
Regards,
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+: first set of PRM/CM cleanups for 3.8
Date: Wed, 24 Oct 2012 17:03:35 -0700 [thread overview]
Message-ID: <20121025000334.GF11928@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1210211912410.26128@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [121021 12:15]:
> Hi Tony
>
> The following changes since commit 6f0c0580b70c89094b3422ba81118c7b959c7556:
>
> Linux 3.7-rc2 (2012-10-20 12:11:32 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git tags/omap-cleanup-a-for-3.8
>
> for you to fetch changes up to 2bb2a5d30abb0dc99d074877bfad2056142c730b:
>
> ARM: OMAP2+: PRM: create PRM reset source API for the watchdog timer driver (2012-10-21 01:01:13 -0600)
>
> ----------------------------------------------------------------
> The first set of OMAP PRM/CM-related cleanup patches for 3.8.
> Prepares for the future move of the PRM/CM code to drivers/. Also
> includes some prcm.[ch] cleanup patches from the WDTIMER cleanup
> series that don't need external acks.
>
> Basic test logs for this branch on top of v3.7-rc2 are here:
>
> http://www.pwsan.com/omap/testlogs/prcm_cleanup_a_3.8/20121021123719/
>
> But due to the number of unrelated regressions present in v3.7-rc[12],
> it's not particularly usable as a testing base. With reverts, fixes,
> and workarounds applied as documented in:
>
> http://www.pwsan.com/omap/testlogs/test_v3.7-rc2/20121020134755/README.txt
>
> the following test logs were obtained:
>
> http://www.pwsan.com/omap/testlogs/prcm_cleanup_a_3.8/20121020231757/
>
> which indicate that the series tests cleanly.
Thanks pulling into omap-for-v3.8/cleanup-prcm.
Regards,
Tony
next prev parent reply other threads:[~2012-10-25 0:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-21 19:13 [GIT PULL] ARM: OMAP2+: first set of PRM/CM cleanups for 3.8 Paul Walmsley
2012-10-21 19:13 ` Paul Walmsley
2012-10-25 0:03 ` Tony Lindgren [this message]
2012-10-25 0:03 ` 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=20121025000334.GF11928@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.