mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Sascha Hauer" <kernel@pengutronix.de>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Jonathan Austin" <jonathan.austin@arm.com>,
	"Catalin Marinas" <catalin.marinas@arm.com>,
	"Arnd Bergmann" <arnd@arndb.de>
Subject: Re: [PATCH v4] irqchip: Add support for ARMv7-M's NVIC
Date: Tue, 25 Jun 2013 14:23:01 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1306251420330.4013@ionos.tec.linutronix.de> (raw)
In-Reply-To: <CACxGe6vBCKCnXRtvT9N6cRPa7uHTJDMw7k-46eCj7fFPko+Raw@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1649 bytes --]

On Tue, 25 Jun 2013, Grant Likely wrote:
> On Tue, Jun 25, 2013 at 11:34 AM, Uwe Kleine-König
> <u.kleine-koenig@pengutronix.de> wrote:
> > Hello Thomas, hello Grant,
> >
> > On Wed, Jun 12, 2013 at 11:50:35PM +0200, Uwe Kleine-König wrote:
> >> This interrupt controller is found on Cortex-M3 and Cortex-M4 machines.
> >>
> >> Support for this controller appeared in Catalin's Cortex tree based on
> >> 2.6.33 but was nearly completely rewritten.
> >>
> >> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> >> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> >> ---
> >>
> >> Notes:
> >>     Changes since v3, sent with
> >>     Message-Id: <1366214540-31166-1-git-send-email-u.kleine-koenig@pengutronix.de>:
> >>
> >>      - use generic chip
> >>      - rename nvic_do_IRQ to nvic_handle_irq
> >>
> >>     This depends on the stuff currently in tip/irq/for-arm
> > I see that tip/irq/for-arm went into next via Grant's irqdomain tree. I
> > assume that means the changes go in for 3.11?
> 
> Yes, the plan is to put that branch into v3.11. I don't know if Thomas
> plans to send a separate pull request for the irq/for-arm branch, or
> if he is going to let it go as part of my pull request. I'll work it

irq/for-arm is in irq/core as well. So whoever sends first will merge
it and the later pull request will just contain the same commits.

> out with him when the merge window opens. It would probably be best
> for your patch to be applied on the irq/for-arm branch and pushed
> separately from my irqdomain branch since I don't maintain any of the
> irqchip drivers.

I can take it via tip/irq/core.

Thanks,

	tglx

  reply	other threads:[~2013-06-25 12:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12 21:50 Uwe Kleine-König
2013-06-12 22:00 ` Uwe Kleine-König
2013-06-14  9:40 ` Catalin Marinas
2013-06-14 14:24 ` Arnd Bergmann
     [not found] ` <20130615004149.D85B13E0A2E@localhost>
2013-06-16  9:21   ` Uwe Kleine-König
2013-06-25 10:34 ` Uwe Kleine-König
2013-06-25 11:04   ` Grant Likely
2013-06-25 12:23     ` Thomas Gleixner [this message]
2013-06-25 21:29 ` Thomas Gleixner

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=alpine.DEB.2.02.1306251420330.4013@ionos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=grant.likely@secretlab.ca \
    --cc=jonathan.austin@arm.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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

all inboxes | Powered by JetHome®