All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Julien Thierry <julien.thierry@arm.com>
Cc: <linux-kernel@vger.kernel.org>, <tglx@linutronix.de>,
	<peterz@infradead.org>, <mingo@kernel.org>
Subject: Re: [PATCH v5 0/4] Provide core API for NMIs
Date: Mon, 28 Jan 2019 16:54:40 +0000	[thread overview]
Message-ID: <86d0ogvi27.wl-marc.zyngier@arm.com> (raw)
In-Reply-To: <1548689907-17124-1-git-send-email-julien.thierry@arm.com>

Hi Julien,

On Mon, 28 Jan 2019 15:38:23 +0000,
Julien Thierry <julien.thierry@arm.com> wrote:
> 
> Hi,
> 
> This patch series provides a way for irqchips to define some IRQs as NMIs.
> 
> Updating this series as it is needed for the arm64 pseudo-NMI[1] which we
> are considering to merge.
> 
> Changes since v4[2]:
> - Rebased on v5.0-rc4
> - Modified comment for request_percpu_nmi() to detail
>   the use of per CPU NMIs a bit more

I think this is starting to look good. If Thomas, Ingo and Peter are
OK with it, we should start talking about the merge strategy of the
humongous arm64 series that depends on this.

Thanks,

	M.

-- 
Jazz is not dead, it just smell funny.

      parent reply	other threads:[~2019-01-28 16:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-28 15:38 [PATCH v5 0/4] Provide core API for NMIs Julien Thierry
2019-01-28 15:38 ` [PATCH v5 1/4] genirq: Provide basic NMI management for interrupt lines Julien Thierry
2019-01-28 16:25   ` Marc Zyngier
2019-01-28 15:38 ` [PATCH v5 2/4] genirq: Provide NMI management for percpu_devid interrupts Julien Thierry
2019-01-28 16:41   ` Marc Zyngier
2019-01-28 17:27     ` Julien Thierry
2019-01-28 15:38 ` [PATCH v5 3/4] genirq: Provide NMI handlers Julien Thierry
2019-01-28 16:42   ` Marc Zyngier
2019-01-28 15:38 ` [PATCH v5 4/4] irqdesc: Add domain handler for NMIs Julien Thierry
2019-01-28 16:46   ` Marc Zyngier
2019-01-28 16:54 ` Marc Zyngier [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=86d0ogvi27.wl-marc.zyngier@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=julien.thierry@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.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 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.