From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] irqchip: Add support for ARMv7-M's NVIC
Date: Tue, 25 Jun 2013 12:34:40 +0200 [thread overview]
Message-ID: <20130625103440.GR11232@pengutronix.de> (raw)
In-Reply-To: <1371073835-10639-1-git-send-email-u.kleine-koenig@pengutronix.de>
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?
Are you OK with my patch? I can resend with the accumulated Acks and the
arch/arm hunk dropped if it helps you. Just tell me what you want.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2013-06-25 10:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 21:50 [PATCH v4] irqchip: Add support for ARMv7-M's NVIC 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
2013-06-15 0:41 ` Grant Likely
2013-06-16 9:21 ` Uwe Kleine-König
2013-06-25 10:34 ` Uwe Kleine-König [this message]
2013-06-25 11:04 ` Grant Likely
2013-06-25 12:23 ` Thomas Gleixner
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=20130625103440.GR11232@pengutronix.de \
--to=u.kleine-koenig@pengutronix.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 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).