linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] Preparatory GIC patches for arm64 support
Date: Thu, 31 Jan 2013 12:32:09 +0000	[thread overview]
Message-ID: <20130131123208.GE12877@arm.com> (raw)
In-Reply-To: <20130131114703.GX23505@n2100.arm.linux.org.uk>

On Thu, Jan 31, 2013 at 11:47:04AM +0000, Russell King - ARM Linux wrote:
> On Thu, Jan 31, 2013 at 10:30:44AM +0000, Catalin Marinas wrote:
> > On Tue, Jan 29, 2013 at 04:18:35PM +0000, Catalin Marinas wrote:
> > > That's the second version of the GIC clean-up patches to support arm64.
> > > The only change from v1 is that the second patch (chained_irq.h) also
> > > covers drivers/gpio and drivers/pinctrl (#include change).
> > 
> > Are you ok to merge this series via the arm-soc tree for 3.9-rc1? There
> > are no complaints so far (only acks ;). This would allow me to push GIC
> > support for arm64.
> 
> So I don't exist anymore to you?

You do ;) and you've been cc'ed on these patches. Just wasn't sure you
care about patches that have 'arm64' in the cover email ;).

Since Rob's series went through the arm-soc, I consider that further
changes should go the same route as there is a dependency and I'd like
to get them merged sooner. These patches touch primarily SoC code, apart
from some trivial code moving and the CPU notifier in irq-gic.c (you are
the original author of this driver) and I'm ok if you want to merge it.

I really don't mind if you or Olof merge the whole series as long as it
gets upstream at some point. As you expressed an opinion on these
patches and you want to merge them, they'll have to wait until after
3.9-rc1 for Rob's patches to get in.

> Catalin, it's already been suggested to you that this series is more
> core ARM stuff than SoC stuff, and it's also been suggested that you
> merge this through my tree.

No, it hasn't. Just Nico saying that he'd prefer *his* series was merged
by RMK (and I agree). A way to sort the dependency issue for Nico is to
at least push some of this series in 3.9-rc1. Otherwise we just postpone
the dependency issue.

> No, I guess this figures after all your excessively negative replies
> on all of my comments during the review of ARM64.

It's all relative - negative reply to negative reply would make it
positive ;).

-- 
Catalin

      reply	other threads:[~2013-01-31 12:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 16:18 [PATCH v2 0/4] Preparatory GIC patches for arm64 support Catalin Marinas
2013-01-29 16:18 ` [PATCH v2 1/4] arm: Move the set_handle_irq and handle_arch_irq declarations to asm/irq.h Catalin Marinas
2013-01-29 16:18 ` [PATCH v2 2/4] arm: Move chained_irq_(enter|exit) to a generic file Catalin Marinas
2013-01-29 16:18 ` [PATCH v2 3/4] irqchip: gic: Call handle_bad_irq() directly Catalin Marinas
2013-01-29 16:18 ` [PATCH v2 4/4] irqchip: gic: Perform the gic_secondary_init() call via CPU notifier Catalin Marinas
2013-01-29 22:35   ` Nicolas Pitre
2013-01-29 23:12     ` Catalin Marinas
2013-01-30  0:11       ` Nicolas Pitre
2013-01-31 11:25         ` Russell King - ARM Linux
2013-01-31 11:49           ` Catalin Marinas
2013-01-31 17:32           ` Nicolas Pitre
2013-01-31 17:55             ` Russell King - ARM Linux
2013-01-31 20:31               ` Nicolas Pitre
2013-02-01 14:38                 ` Jon Medhurst (Tixy)
2013-02-01 17:39                   ` Nicolas Pitre
2013-01-30  0:31   ` Dinh Nguyen
2013-01-31 10:30 ` [PATCH v2 0/4] Preparatory GIC patches for arm64 support Catalin Marinas
2013-01-31 11:47   ` Russell King - ARM Linux
2013-01-31 12:32     ` Catalin Marinas [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=20130131123208.GE12877@arm.com \
    --to=catalin.marinas@arm.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).