linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: ARMv7-M: Fix name of NVIC handler function
Date: Tue, 30 Jul 2013 11:26:44 +0100	[thread overview]
Message-ID: <20130730102643.GP24642@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130730081507.GO1754@pengutronix.de>

On Tue, Jul 30, 2013 at 10:15:07AM +0200, Uwe Kleine-K?nig wrote:
> Hi Russell,
> 
> On Mon, Jul 08, 2013 at 05:29:17PM +0200, Uwe Kleine-K?nig wrote:
> > On Wed, Jun 26, 2013 at 11:27:35AM +0200, Uwe Kleine-K?nig wrote:
> > > The name changed in response to review comments for the nvic irqchip
> > > driver when the original name was already accepted into Russell King's
> > > tree.
> > > 
> > > Signed-off-by: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>
> > > ---
> > > Hello,
> > > 
> > > this patch was part of the irqchip patch v4, but I split it out for
> > > being easier to merge in v5. It applies on top of Russell's devel-stable
> > > branch.
> > > 
> > > Russell: I put it on top of my for-next branch (
> > > 
> > > 	git://git.pengutronix.de/git/ukl/linux.git for-next
> > > 
> > > ) that you merged into your devel-stable some time ago. So assuming
> > > you're fine with the patch, you can just repull or I can put it into
> > > your patch tracker if you prefer it. In the latter case please tell me.
> > The mismatch hit Linus' tree now. How should this patch get to him?
> Although it's not critical (as there are no in-tree users) I still think
> this should go in before 3.11.

Can you put it in the patch system please?

      reply	other threads:[~2013-07-30 10:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-26  9:27 [PATCH] ARM: ARMv7-M: Fix name of NVIC handler function Uwe Kleine-König
2013-07-08 15:29 ` Uwe Kleine-König
2013-07-30  8:15   ` Uwe Kleine-König
2013-07-30 10:26     ` Russell King - ARM Linux [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=20130730102643.GP24642@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).