linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/3] omap platform and board related late patches for v3.7 merge window
Date: Mon, 24 Sep 2012 17:39:53 -0700	[thread overview]
Message-ID: <20120925003953.GQ28835@atomide.com> (raw)
In-Reply-To: <E1TGGAI-0000D1-T0@merlin.infradead.org>

* Tony Lindgren <tony@atomide.com> [120924 14:30]:
> The following changes since commit 0e70156de4c8465bfb8cb45cdc1bbc2fa474ce14:
> 
>   ARM: OMAP2+: Make omap4-keypad.h local (2012-09-20 15:04:04 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-devel-board-late-v2-for-v3.7
> 
> for you to fetch changes up to ead53717d9ab28c942b9adf66f8c02442dbfbc8a:
> 
>   arm: make FORCE_MAX_ZONEORDER configurable for TI AM33XX (2012-09-24 10:32:39 -0700)
> 
> ----------------------------------------------------------------
> These board and platform related patches have been posted
> quite a while ago but have somehow fallen though the cracks
> as most of the focus has been making things to work with
> device tree. As the first patch depends on sparse IRQ
> related removal of irqs.h and related header moves, these
> are based on omap-cleanup-local-headers-for-v3.7 tag.

Let's scrap this pull request, Russell noted that Yegor's patch
breaks sa1111.

Regards,

Tony
 
> ----------------------------------------------------------------
> AnilKumar Ch (1):
>       ARM: OMAP2+: serial: Change MAX_HSUART_PORTS to 6
> 
> Peter Ujfalusi (1):
>       ARM: OMAP4: twl-common: Support for additional devices on i2c1 bus
> 
> Yegor Yefremov (1):
>       arm: make FORCE_MAX_ZONEORDER configurable for TI AM33XX


 
>  arch/arm/Kconfig                              |    5 ++--
>  arch/arm/mach-omap2/board-4430sdp.c           |   12 ++++++--
>  arch/arm/mach-omap2/board-omap4panda.c        |   12 ++++++--
>  arch/arm/mach-omap2/twl-common.c              |   37 ++++++++-----------------
>  arch/arm/mach-omap2/twl-common.h              |    3 +-
>  arch/arm/plat-omap/include/plat/omap-serial.h |    2 +-
>  6 files changed, 37 insertions(+), 34 deletions(-)
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2012-09-25  0:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-24 21:25 [GIT PULL 1/3] omap clock late patches for v3.7 merge window Tony Lindgren
2012-09-24 21:25 ` [GIT PULL 2/3] omap platform and board related " Tony Lindgren
2012-09-24 21:25 ` [GIT PULL 3/3] omap arch timer late changes " Tony Lindgren
2012-09-24 21:30 ` [GIT PULL 1/3] omap clock late patches " Tony Lindgren
     [not found] ` <E1TGGAI-0000D1-T0@merlin.infradead.org>
2012-09-25  0:39   ` Tony Lindgren [this message]
2012-09-25  3:31     ` [GIT PULL 2/3] omap platform and board related " Tony Lindgren
2012-09-29 21:03       ` Olof Johansson
2012-09-30 18:17         ` Tony Lindgren
     [not found] ` <5060cfe6.8187e50a.7ef1.ffff8d51SMTPIN_ADDED@mx.google.com>
2012-09-29 20:58   ` [GIT PULL 3/3] omap arch timer late changes " 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=20120925003953.GQ28835@atomide.com \
    --to=tony@atomide.com \
    --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;
as well as URLs for NNTP newsgroup(s).