linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 AM33xx: fixes and IP block integration support for 3.9
Date: Sun, 10 Feb 2013 09:07:24 -0800	[thread overview]
Message-ID: <20130210170724.GJ4801@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1302081720360.28008@utopia.booyaka.com>

* Paul Walmsley <paul@pwsan.com> [130208 09:25]:
> Hi Tony,
> 
> The following changes since commit 88b62b915b0b7e25870eb0604ed9a92ba4bfc9f7:
> 
>   Linux 3.8-rc6 (2013-02-01 12:08:14 +1100)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git tags/omap-devel-a-for-3.9
> 
> for you to fetch changes up to 169c82a294e3722eb1e82b7dac58b35fe2119b80:
> 
>   ARM: OMAP2: am33xx-hwmod: Fix "register offset NULL check" bug (2013-02-08 08:21:13 -0700)
> 
> ----------------------------------------------------------------
> Fixes and IP block support for the TI AM33xx family of SoCs.  These
> are prerequisites for power management and some PWM driver changes.
> 
> Basic test logs are available from:
> 
>    http://www.pwsan.com/omap/testlogs/am33xx_fixes_a_3.9/20130208084835/
> 
> although it must be noted that I am unable to test these patches on
> AM33xx due to an unknown problem with v3.8-rc kernels:
> 
>    http://www.mail-archive.com/linux-omap@vger.kernel.org/msg83525.html
> 

Thanks pulled into omap-for-v3.9/am33xx.

Tony

      reply	other threads:[~2013-02-10 17:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08 17:21 [GIT PULL] ARM: OMAP AM33xx: fixes and IP block integration support for 3.9 Paul Walmsley
2013-02-10 17:07 ` 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=20130210170724.GJ4801@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).