Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Abhin Parekadan Jose <abhinjoses@gmail.com>
Cc: lukas@wunner.de, mst@redhat.com, virtualization@lists.linux.dev,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	bhelgaas@google.com, kbusch@kernel.org, stefanha@redhat.com,
	parav@nvidia.com, axboe@kernel.dk, kees@kernel.org,
	ilpo.jarvinen@linux.intel.com, xueshuai@linux.alibaba.com
Subject: Re: [PATCH RFC 0/3] pci_hp: fix surprise removal hang during safe removal
Date: Wed, 26 Aug 2026 14:48:15 -0500	[thread overview]
Message-ID: <20260826194815.GA1552818@bhelgaas> (raw)
In-Reply-To: <20260823183458.982699-1-abhinjoses@gmail.com>

On Sun, Aug 23, 2026 at 06:34:52PM +0000, Abhin Parekadan Jose wrote:
> This series is based on top of MST's RFC v5
> (cover.1752094439.git.mst@redhat.com) and tries to address the architectural
> gap identified by Lukas Wunner in that thread.

This is going to get lost because it's buried in the middle of a
virtio thread that's been dormant for a while.  Can this be pulled out
along with any dependencies from Michael's series, so it's purely PCI
and posted separately?  Also please observe the drivers/pci commit log
and subject line conventions.

      parent reply	other threads:[~2026-08-26 19:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1752094439.git.mst@redhat.com>
2025-07-09 20:55 ` [PATCH RFC v5 1/5] pci: report surprise removal event Michael S. Tsirkin
2025-07-09 23:38   ` Bjorn Helgaas
2025-07-09 23:55     ` Keith Busch
2025-07-14  6:17       ` Michael S. Tsirkin
2025-07-14  6:26     ` Michael S. Tsirkin
2025-07-14 21:13       ` Bjorn Helgaas
2025-07-15  6:28         ` Michael S. Tsirkin
2025-07-16 22:29           ` Bjorn Helgaas
2025-07-17 15:15             ` Michael S. Tsirkin
2025-07-14  6:11   ` Lukas Wunner
2025-07-14  6:18     ` Michael S. Tsirkin
2025-07-14  6:54     ` Michael S. Tsirkin
2025-07-17 15:11     ` Michael S. Tsirkin
2025-07-17 20:12       ` Lukas Wunner
2025-07-17 23:31         ` Michael S. Tsirkin
2025-07-18  4:35           ` Lukas Wunner
2025-07-18  8:40             ` Michael S. Tsirkin
2026-08-23 18:34 ` [PATCH RFC 0/3] pci_hp: fix surprise removal hang during safe removal Abhin Parekadan Jose
2026-08-23 18:34   ` [PATCH RFC 1/3] misc: add edu_srpoc surprise removal POC driver Abhin Parekadan Jose
2026-08-23 18:44     ` sashiko-bot
2026-08-23 18:34   ` [PATCH RFC 2/3] pciehp: add disconnect_work work_struct Abhin Parekadan Jose
2026-08-23 18:44     ` sashiko-bot
2026-08-23 18:34   ` [PATCH RFC 3/3] pciehp_hpc: workaround to not wait in pciehp_isr on surprise removal Abhin Parekadan Jose
2026-08-23 18:44     ` sashiko-bot
2026-08-26 19:48   ` Bjorn Helgaas [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=20260826194815.GA1552818@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=abhinjoses@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=bhelgaas@google.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=kbusch@kernel.org \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=mst@redhat.com \
    --cc=parav@nvidia.com \
    --cc=stefanha@redhat.com \
    --cc=virtualization@lists.linux.dev \
    --cc=xueshuai@linux.alibaba.com \
    /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