All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/7] Initial Calxeda Highbank support
Date: Fri, 30 Sep 2011 22:31:36 +0200	[thread overview]
Message-ID: <201109302231.36215.arnd@arndb.de> (raw)
In-Reply-To: <4E80C6D1.1010601@gmail.com>

On Monday 26 September 2011, Rob Herring wrote:
> Any comments on v2?
> 
> The GIC binding series seems to be firming up. As myself and several
> others are dependent on it, I was planning to send both through arm-soc
> tree as 2 pulls. I also have some dependencies on rmk's tree with l2x0
> DT support and mach header clean-ups.

Looks all good as far as I can tell. Please send the pull requests.

	Arnd

      reply	other threads:[~2011-09-30 20:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-01  1:43 [PATCH v2 0/7] Initial Calxeda Highbank support Rob Herring
2011-09-01  1:44 ` [PATCH 1/7] ARM: l2x0: add empty l2x0_of_init Rob Herring
2011-09-01  3:36   ` Barry Song
2011-09-01  3:58     ` Rob Herring
2011-09-01  1:44 ` [PATCH v2 2/7] ARM: highbank: add devicetree source Rob Herring
2011-09-01  1:44 ` [PATCH v2 3/7] ARM: add Highbank core platform support Rob Herring
2011-09-01  1:44 ` [PATCH v2 4/7] MAINTAINERS: add Calxeda Highbank ARM platform Rob Herring
2011-09-01  1:44 ` [PATCH v2 5/7] ARM: highbank: add SMP support Rob Herring
2011-09-06  1:01   ` Shawn Guo
2011-10-05 16:00     ` Rob Herring
2011-10-07 12:40       ` Shawn Guo
2011-09-01  1:44 ` [PATCH v2 6/7] ARM: highbank: Add cpu hotplug support Rob Herring
2011-09-01  1:44 ` [PATCH v2 7/7] ARM: highbank: add suspend support Rob Herring
2011-09-01 12:22   ` Shawn Guo
2011-09-01 21:39     ` Rob Herring
2011-09-01 14:00 ` [PATCH v2 0/7] Initial Calxeda Highbank support Jamie Iles
2011-09-26 18:39 ` Rob Herring
2011-09-30 20:31   ` Arnd Bergmann [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=201109302231.36215.arnd@arndb.de \
    --to=arnd@arndb.de \
    --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 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.