All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Ene <sebastianene@google.com>
To: Marc Zyngier <maz@kernel.org>
Cc: arnd@arndb.de, gregkh@linuxfoundation.org, will@kernel.org,
	Rob Herring <robh+dt@kernel.org>,
	Dragan Cvetic <dragan.cvetic@xilinx.com>,
	Guenter Roeck <linux@roeck-us.net>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	kernel-team@android.com
Subject: Re: [PATCH v2 0/2] misc: vcpu_stall_detector: Add a PPI interrupt
Date: Thu, 13 Jun 2024 16:44:23 +0000	[thread overview]
Message-ID: <Zmsh53PnONKG23MC@google.com> (raw)
In-Reply-To: <86tthwki93.wl-maz@kernel.org>

On Thu, Jun 13, 2024 at 03:52:08PM +0100, Marc Zyngier wrote:
> On Thu, 13 Jun 2024 15:13:33 +0100,
> Sebastian Ene <sebastianene@google.com> wrote:
> > 
> > Hello,
> > 
> > I respined the v2 version to address an issue previously found here:
> > https://lore.kernel.org/all/202406132132.FBKSWFav-lkp@intel.com/
> 
> So is this v2 or v3? Having two v2s on the list is... confusing.
> 
> 	M.
> 

There is a small change in the patch 2/2 so you are right it should be v3,
sorry for the confusion.

> -- 
> Without deviation from the norm, progress is not possible.

Thanks,
Seb

  reply	other threads:[~2024-06-13 16:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 14:13 [PATCH v2 0/2] misc: vcpu_stall_detector: Add a PPI interrupt Sebastian Ene
2024-06-13 14:13 ` [PATCH v2 1/2] dt-bindings: vcpu_stall_detector: Add a PPI interrupt to the virtual device Sebastian Ene
2024-06-13 14:13 ` [PATCH v2 2/2] misc: Register a PPI for the vcpu stall detection " Sebastian Ene
2024-06-13 14:52 ` [PATCH v2 0/2] misc: vcpu_stall_detector: Add a PPI interrupt Marc Zyngier
2024-06-13 16:44   ` Sebastian Ene [this message]
2024-07-03 14:34     ` Greg KH
2024-07-03 15:00       ` Sebastian Ene
  -- strict thread matches above, loose matches on Subject: below --
2024-06-11 11:01 Sebastian Ene

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=Zmsh53PnONKG23MC@google.com \
    --to=sebastianene@google.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=dragan.cvetic@xilinx.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=maz@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=will@kernel.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.