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] Preparatory GIC patches for arm64 support
Date: Tue, 2 Apr 2013 11:03:39 -0700	[thread overview]
Message-ID: <20130402180339.GJ25867@quad.lixom.net> (raw)
In-Reply-To: <20130328140239.GF24039@arm.com>

On Thu, Mar 28, 2013 at 02:02:39PM +0000, Catalin Marinas wrote:
> Hi,
> 
> As I'm about to go on holiday for two weeks and I haven't heard any
> preference for who should be merging these patches, I'm sending the pull
> request to arm-soc given that 90% of the changes target SoC code. Apart
> from the gic_secondary_init() patch, the rest is trivial header code
> moving around or removal.
> 
> Russell, if you have any objections, please let arm-soc guys and me know
> and feel free to pull these patches via your tree. I don't mind either
> way.
> 
> Thanks,
> 
> Catalin
> 
> 
> The following changes since commit a937536b868b8369b98967929045f1df54234323:
> 
>   Linux 3.9-rc3 (2013-03-17 15:59:32 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/linux-aarch64.git gic


Pulled as gic/cleanup into next/cleanup.

I got a handful of context conflicts due to additions near the old
secondary_init functions, and one add/add conflict on includes. All trivial to
resolve.


-Olof

  parent reply	other threads:[~2013-04-02 18:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28 14:02 [GIT PULL] Preparatory GIC patches for arm64 support Catalin Marinas
2013-03-28 14:24 ` Russell King - ARM Linux
2013-04-02 18:03 ` Olof Johansson [this message]
2013-04-02 22:11   ` 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=20130402180339.GJ25867@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