public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/3] omap non-urgent fixes for v3.20
Date: Wed, 21 Jan 2015 16:49:57 -0800	[thread overview]
Message-ID: <20150122004957.GD29014@quad.lixom.net> (raw)
In-Reply-To: <54b99dd1.a21a450a.3fbf.25c5SMTPIN_ADDED_BROKEN@mx.google.com>

On Fri, Jan 16, 2015 at 03:21:20PM -0800, Tony Lindgren wrote:
> The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672:
> 
>   Linux 3.19-rc1 (2014-12-20 17:08:50 -0800)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.20/fixes-not-urgent-pt1
> 
> for you to fetch changes up to 13efcb188984f69e1f97b4d9e7d3663fb782946f:
> 
>   ARM: OMAP2+: Disable omap3 PM init for ti81xx (2015-01-14 17:37:16 -0800)
> 
> ----------------------------------------------------------------
> Non-urgent fixes for omap variant dm816x that has been in a sorry
> broken half merged state for a few years now. This gets us to the
> point where we can boot it properly once the related SoC data is
> added. Note that we've already made dm816x device tree only by
> removing the known broken board file.
> 
> ----------------------------------------------------------------
> Tony Lindgren (6):
>       ARM: OMAP2+: Fix error handling for omap2_clk_enable_init_clocks
>       ARM: OMAP2+: Fix ti81xx devtype
>       ARM: OMAP2+: Fix ti81xx class type
>       ARM: OMAP2+: Fix dm814 and dm816 for clocks and timer init
>       ARM: OMAP2+: Fix reboot for 81xx
>       ARM: OMAP2+: Disable omap3 PM init for ti81xx

Merged, thanks.

-Olof

       reply	other threads:[~2015-01-22  0:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <54b99dd1.a21a450a.3fbf.25c5SMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-22  0:49 ` Olof Johansson [this message]
2015-01-16 23:21 [GIT PULL 1/3] omap non-urgent fixes for v3.20 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=20150122004957.GD29014@quad.lixom.net \
    --to=olof@lixom.net \
    --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