All of lore.kernel.org
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH 4.0-rc7 v20 0/6] irq/arm: Implement arch_trigger_all_cpu_backtrace
Date: Tue, 21 Apr 2015 14:08:00 +0100	[thread overview]
Message-ID: <55364BB0.6060108@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1504211445010.13914@nanos>

On 21/04/15 13:46, Thomas Gleixner wrote:
> On Fri, 10 Apr 2015, Daniel Thompson wrote:
> 
>> Jason/Thomas:
>>   Any chance of taking the first five of these patches via the irqchip
>>   route? The x86 patch has an ack from Ingo, printk has no explicit
>>   maintainer and I've done plenty of bisectability tests on the patchset
>>   so leaving the last patch for the next dev. cycle should be no
>>   trouble.
> 
> First of all I need an acked/reviewed from Marc or Russell,
> preferrably both of them.

I'm on it.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <marc.zyngier@arm.com>
To: Thomas Gleixner <tglx@linutronix.de>,
	Daniel Thompson <daniel.thompson@linaro.org>
Cc: linaro-kernel@lists.linaro.org,
	Russell King <linux@arm.linux.org.uk>,
	Jason Cooper <jason@lakedaemon.net>,
	patches@linaro.org, Stephen Boyd <sboyd@codeaurora.org>,
	Will Deacon <will.deacon@arm.com>,
	linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>,
	Daniel Drake <drake@endlessm.com>,
	Dmitry Pervushin <dpervushin@gmail.com>,
	Dirk Behme <dirk.behme@de.bosch.com>,
	John Stultz <john.stultz@linaro.org>,
	Tim Sander <tim@krieglstein.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Sumit Semwal <sumit.semwal@linaro.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RESEND PATCH 4.0-rc7 v20 0/6] irq/arm: Implement arch_trigger_all_cpu_backtrace
Date: Tue, 21 Apr 2015 14:08:00 +0100	[thread overview]
Message-ID: <55364BB0.6060108@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1504211445010.13914@nanos>

On 21/04/15 13:46, Thomas Gleixner wrote:
> On Fri, 10 Apr 2015, Daniel Thompson wrote:
> 
>> Jason/Thomas:
>>   Any chance of taking the first five of these patches via the irqchip
>>   route? The x86 patch has an ack from Ingo, printk has no explicit
>>   maintainer and I've done plenty of bisectability tests on the patchset
>>   so leaving the last patch for the next dev. cycle should be no
>>   trouble.
> 
> First of all I need an acked/reviewed from Marc or Russell,
> preferrably both of them.

I'm on it.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2015-04-21 13:08 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 16:53 [PATCH 4.0-rc5 v19 0/6] irq/arm: Implement arch_trigger_all_cpu_backtrace Daniel Thompson
2015-03-24 16:53 ` Daniel Thompson
2015-03-24 16:53 ` [PATCH 4.0-rc5 v19 1/6] irqchip: gic: Optimize locking in gic_raise_softirq Daniel Thompson
2015-03-24 16:53   ` Daniel Thompson
2015-03-24 16:53 ` [PATCH 4.0-rc5 v19 2/6] irqchip: gic: Make gic_raise_softirq FIQ-safe Daniel Thompson
2015-03-24 16:53   ` Daniel Thompson
2015-03-24 16:53 ` [PATCH 4.0-rc5 v19 3/6] irqchip: gic: Introduce plumbing for IPI FIQ Daniel Thompson
2015-03-24 16:53   ` Daniel Thompson
2015-03-24 16:53 ` [PATCH 4.0-rc5 v19 4/6] printk: Simple implementation for NMI backtracing Daniel Thompson
2015-03-24 16:53   ` Daniel Thompson
2015-03-24 16:53 ` [PATCH 4.0-rc5 v19 5/6] x86/nmi: Use common printk functions Daniel Thompson
2015-03-24 16:53   ` Daniel Thompson
2015-03-24 16:53 ` [PATCH 4.0-rc5 v19 6/6] ARM: Add support for on-demand backtrace of other CPUs Daniel Thompson
2015-03-24 16:53   ` Daniel Thompson
2015-04-07 15:37 ` [RESEND PATCH 4.0-rc5 v19 0/6] irq/arm: Implement arch_trigger_all_cpu_backtrace Daniel Thompson
2015-04-07 15:37   ` Daniel Thompson
2015-04-07 15:37   ` [RESEND PATCH 4.0-rc5 v19 1/6] irqchip: gic: Optimize locking in gic_raise_softirq Daniel Thompson
2015-04-07 15:37     ` Daniel Thompson
2015-04-07 15:37   ` [RESEND PATCH 4.0-rc5 v19 2/6] irqchip: gic: Make gic_raise_softirq FIQ-safe Daniel Thompson
2015-04-07 15:37     ` Daniel Thompson
2015-04-07 15:38   ` [RESEND PATCH 4.0-rc5 v19 3/6] irqchip: gic: Introduce plumbing for IPI FIQ Daniel Thompson
2015-04-07 15:38     ` Daniel Thompson
2015-04-07 15:38   ` [RESEND PATCH 4.0-rc5 v19 4/6] printk: Simple implementation for NMI backtracing Daniel Thompson
2015-04-07 15:38     ` Daniel Thompson
2015-04-07 15:38   ` [RESEND PATCH 4.0-rc5 v19 5/6] x86/nmi: Use common printk functions Daniel Thompson
2015-04-07 15:38     ` Daniel Thompson
2015-04-07 16:19     ` Steven Rostedt
2015-04-07 16:19       ` Steven Rostedt
2015-04-07 16:37       ` Borislav Petkov
2015-04-07 16:37         ` Borislav Petkov
2015-04-07 16:43         ` Steven Rostedt
2015-04-07 16:43           ` Steven Rostedt
2015-04-08 12:08           ` Daniel Thompson
2015-04-08 12:08             ` Daniel Thompson
2015-04-07 15:38   ` [RESEND PATCH 4.0-rc5 v19 6/6] ARM: Add support for on-demand backtrace of other CPUs Daniel Thompson
2015-04-07 15:38     ` Daniel Thompson
2015-04-10  9:51 ` [RESEND PATCH 4.0-rc7 v20 0/6] irq/arm: Implement arch_trigger_all_cpu_backtrace Daniel Thompson
2015-04-10  9:51   ` Daniel Thompson
2015-04-10  9:51   ` [RESEND PATCH 4.0-rc7 v20 1/6] irqchip: gic: Optimize locking in gic_raise_softirq Daniel Thompson
2015-04-10  9:51     ` Daniel Thompson
2015-04-21 12:51     ` Marc Zyngier
2015-04-21 12:51       ` Marc Zyngier
2015-04-10  9:51   ` [RESEND PATCH 4.0-rc7 v20 2/6] irqchip: gic: Make gic_raise_softirq FIQ-safe Daniel Thompson
2015-04-10  9:51     ` Daniel Thompson
2015-04-21 12:54     ` Marc Zyngier
2015-04-21 12:54       ` Marc Zyngier
2015-04-10  9:51   ` [RESEND PATCH 4.0-rc7 v20 3/6] irqchip: gic: Introduce plumbing for IPI FIQ Daniel Thompson
2015-04-10  9:51     ` Daniel Thompson
2015-04-21 13:45     ` Marc Zyngier
2015-04-21 13:45       ` Marc Zyngier
2015-04-21 21:03       ` Daniel Thompson
2015-04-21 21:03         ` Daniel Thompson
2015-04-22  9:15         ` Marc Zyngier
2015-04-22  9:15           ` Marc Zyngier
2015-04-22 12:45           ` Daniel Thompson
2015-04-22 12:45             ` Daniel Thompson
2015-04-22 12:57             ` Marc Zyngier
2015-04-22 12:57               ` Marc Zyngier
2015-04-22 15:40               ` Daniel Thompson
2015-04-22 15:40                 ` Daniel Thompson
2015-04-21 14:50     ` Mark Rutland
2015-04-21 14:50       ` Mark Rutland
2015-04-21 21:15       ` Daniel Thompson
2015-04-21 21:15         ` Daniel Thompson
2015-04-22 10:38         ` Mark Rutland
2015-04-22 10:38           ` Mark Rutland
2015-07-02 13:31           ` Daniel Thompson
2015-07-02 13:31             ` Daniel Thompson
2015-04-10  9:51   ` [RESEND PATCH 4.0-rc7 v20 4/6] printk: Simple implementation for NMI backtracing Daniel Thompson
2015-04-10  9:51     ` Daniel Thompson
2015-04-10  9:51   ` [RESEND PATCH 4.0-rc7 v20 5/6] x86/nmi: Use common printk functions Daniel Thompson
2015-04-10  9:51     ` Daniel Thompson
2015-04-10  9:51   ` [RESEND PATCH 4.0-rc7 v20 6/6] ARM: Add support for on-demand backtrace of other CPUs Daniel Thompson
2015-04-10  9:51     ` Daniel Thompson
2015-04-10 10:47   ` [RESEND PATCH 4.0-rc7 v20 0/6] irq/arm: Implement arch_trigger_all_cpu_backtrace Daniel Thompson
2015-04-10 10:47     ` Daniel Thompson
2015-04-21 12:46   ` Thomas Gleixner
2015-04-21 12:46     ` Thomas Gleixner
2015-04-21 13:08     ` Marc Zyngier [this message]
2015-04-21 13:08       ` Marc Zyngier

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=55364BB0.6060108@arm.com \
    --to=marc.zyngier@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.