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 4/4] irqchip: gic: Perform the gic_secondary_init() call via CPU notifier
Date: Thu, 31 Jan 2013 11:49:36 +0000	[thread overview]
Message-ID: <20130131114935.GD12877@arm.com> (raw)
In-Reply-To: <20130131112538.GW23505@n2100.arm.linux.org.uk>

On Thu, Jan 31, 2013 at 11:25:38AM +0000, Russell King - ARM Linux wrote:
> On Tue, Jan 29, 2013 at 07:11:56PM -0500, Nicolas Pitre wrote:
> > On Tue, 29 Jan 2013, Catalin Marinas wrote:
> > > I would like to get them in as soon as possible (ideally 3.9) as AArch64
> > > needs GIC support. I can base them on Rob's branch (already in -next)
> > > and send them the same route (the arm-soc tree if Olof/Arnd are ok to
> > > take them).
> > 
> > Well...  I'd prefer if my series was merged by RMK since this is mostly 
> > core ARM code.  That is posing dependency issues.
> > 
> > I think I'll just ignore your change for now and we'll fix things up 
> > during the v3.9-rc period.
> 
> Given that the ARM kernel seems to be rather broken at the moment, that's
> not going to happen until the 32-bit kernel gets some loving attention to
> make it work again.
> 
> Our primary responsibility is not to stuff the kernel with new features
> as quickly as we possibly can.  It's to make sure that the kernel works,
> and at the moment, it doesn't.  I'm not talking about ancient architectures.
> I'm talking about platforms using ARMv6 and above - platforms with the GIC
> which I'd be able to test this change on.

FWIW, I tested this on vexpress with CA9x4 tile with both 3.8-rc3 (Rob's
branch) and latest linux-next.

If you want to test this change for longer, I'm ok to leave it for 3.10
and stick it in -next at some point (after 3.9-rc1 since there are many
conflicts). I'd like however to push the other trivial code-moving
patches in this series.

-- 
Catalin

  reply	other threads:[~2013-01-31 11:49 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 [this message]
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

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=20130131114935.GD12877@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).