public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: torvalds@linux-foundation.org
Cc: olof@lixom.net, arm@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] ARM: SoC fixes for 3.12-rc
Date: Sun, 13 Oct 2013 09:43:33 -0700	[thread overview]
Message-ID: <20131013164333.GA10894@quad.lixom.net> (raw)

Hi Linus,


The following changes since commit d0e639c9e06d44e713170031fe05fb60ebe680af:

  Linux 3.12-rc4 (2013-10-06 14:00:20 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/fixes-for-linus

for you to fetch changes up to 4d594dd3028ba8cdfcbd854bde3811a1ee4e36d7:

  ARM: exynos: dts: Update 5250 arch timer node with clock frequency (2013-10-13 09:33:54 -0700)

----------------------------------------------------------------
ARM: SoC fixes for 3.12-rc

A small batch of fixes this week, mostly OMAP related. Nothing stands out
as particularly controversial.

Also a fix for a 3.12-rc1 timer regression for Exynos platforms, including
the Chromebooks.

----------------------------------------------------------------
Aaro Koskinen (1):
      ARM: OMAP2: gpmc-onenand: fix sync mode setup with DT

Nishanth Menon (1):
      ARM: OMAP3: Fix hardware detection for omap3630 when booted with device tree

Olof Johansson (1):
      Merge tag 'fixes-against-v3.12-rc3-take2' of git://git.kernel.org/.../tmlind/linux-omap into fixes

Pali Rohár (1):
      ARM: OMAP2: RX-51: Add missing max_current to rx51_lp5523_led_config

Simon Barth (1):
      ARM: mach-omap2: board-generic: fix undefined symbol

Tony Lindgren (1):
      ARM: dts: Fix pinctrl mask for omap3

Yuvaraj Kumar C D (1):
      ARM: exynos: dts: Update 5250 arch timer node with clock frequency

 arch/arm/boot/dts/exynos5250.dtsi            |  5 +++++
 arch/arm/boot/dts/omap3-beagle-xm.dts        |  2 +-
 arch/arm/boot/dts/omap3.dtsi                 |  4 ++--
 arch/arm/mach-omap2/board-generic.c          | 18 ++++++++++++++++++
 arch/arm/mach-omap2/board-rx51-peripherals.c |  9 +++++++++
 arch/arm/mach-omap2/gpmc-onenand.c           | 12 +++++++++++-
 arch/arm/mach-omap2/mux.h                    |  4 +---
 arch/arm/mach-omap2/timer.c                  |  4 ++--
 include/dt-bindings/pinctrl/omap.h           |  4 +---
 9 files changed, 50 insertions(+), 12 deletions(-)

             reply	other threads:[~2013-10-13 16:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-13 16:43 Olof Johansson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-10-25 10:21 [GIT PULL] ARM: SoC fixes for 3.12-rc Olof Johansson
2013-10-03  4:15 Olof Johansson
2013-09-19 19:47 Olof Johansson
2013-09-19 21:39 ` Woodhouse, David
2013-09-19 22:12   ` Olof Johansson
2013-09-19 22:57   ` Brian Norris
2013-09-19 23:19     ` Woodhouse, David
2013-09-20  0:44       ` Brian Norris
2013-09-27 10:59         ` Woodhouse, David
2013-09-27 17:40           ` Brian Norris
2013-10-03  5:02       ` Brian Norris
2013-09-12 20:01 Olof Johansson

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=20131013164333.GA10894@quad.lixom.net \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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