From: Farhan Ali <alifm@linux.ibm.com>
To: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Cc: helgaas@kernel.org, alex@shazbot.org, schnelle@linux.ibm.com,
mjrosato@linux.ibm.com
Subject: Re: [PATCH v22 0/4] [PCI] Error recovery for vfio-pci devices on s390x
Date: Thu, 30 Jul 2026 09:27:04 -0700 [thread overview]
Message-ID: <01d69d29-e20d-48f7-b4fd-d6a88cd64cc9@linux.ibm.com> (raw)
In-Reply-To: <20260720192505.2957-1-alifm@linux.ibm.com>
Hi Bjorn,
Polite ping for these patches. I would like some guidance on how should
we proceed with this series.
Thanks
Farhan
On 7/20/2026 12:25 PM, Farhan Ali wrote:
> Hi Bjorn,
>
> This patch set includes only the PCI patches of the original series for
> error recovery for vfio-pci devices on s390x [1]. Breaking up the patch
> series into PCI and VFIO only patches to make merging easier based on
> discussion with Alex [2].
>
> Thanks
> Farhan
>
> [1] https://lore.kernel.org/all/20260520171113.1111-1-alifm@linux.ibm.com/
> [2] https://lore.kernel.org/all/20260602163344.1eda12d2@shazbot.org/
>
> ChangeLog
> ---------
> v21: https://lore.kernel.org/all/20260630164807.643-1-alifm@linux.ibm.com/
> v21 -> v22
> - Ammend commit message for patch 1.
> - Rebase on 7.2-rc4
>
> v20 https://lore.kernel.org/all/20260622171840.1618-1-alifm@linux.ibm.com/
> v20 -> v21
> - Amend commit message to include Fixes tag and cc stable (patch 4).
> - Rebase on 7.2-rc1.
>
> v19 https://lore.kernel.org/all/20260615183524.2880-1-alifm@linux.ibm.com/
> v19 -> v20
> - Unconditionally enable Memory bit while restoring MSI-X (patch 4).
> Fixes an issue found with sashiko.
>
> v18 https://lore.kernel.org/all/20260603181647.2215-1-alifm@linux.ibm.com/
> v18 -> v19
> - Move config space accessible check to pcie_flr() function (based on
> discussion of Sashiko review)
>
> - Fix a gap in MSI-X restoration (patch 4).
>
> - Rebase on 7.1-rc7
>
> v17 -> v18
> - Rebase on 7.1-rc6.
>
> Farhan Ali (4):
> PCI: Allow per function PCI slots to fix slot reset on s390
> PCI: Avoid saving config space state if inaccessible
> PCI: Fail FLR when config space is inaccessible
> PCI/MSI: Enable memory decoding before restoring MSI-X messages
>
> drivers/pci/hotplug/rpaphp_slot.c | 2 +-
> drivers/pci/msi/msi.c | 10 ++++++++++
> drivers/pci/pci.c | 32 ++++++++++++++++++++++++++++--
> drivers/pci/slot.c | 33 +++++++++++++++++++++++--------
> include/linux/pci.h | 8 ++++++--
> 5 files changed, 72 insertions(+), 13 deletions(-)
>
prev parent reply other threads:[~2026-07-30 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 19:25 [PATCH v22 0/4] [PCI] Error recovery for vfio-pci devices on s390x Farhan Ali
2026-07-20 19:25 ` [PATCH v22 1/4] PCI: Allow per function PCI slots to fix slot reset on s390 Farhan Ali
2026-07-20 19:39 ` sashiko-bot
2026-07-31 0:22 ` Bjorn Helgaas
2026-07-20 19:25 ` [PATCH v22 2/4] PCI: Avoid saving config space state if inaccessible Farhan Ali
2026-07-20 19:42 ` sashiko-bot
2026-07-20 19:25 ` [PATCH v22 3/4] PCI: Fail FLR when config space is inaccessible Farhan Ali
2026-07-20 19:38 ` sashiko-bot
2026-07-20 19:25 ` [PATCH v22 4/4] PCI/MSI: Enable memory decoding before restoring MSI-X messages Farhan Ali
2026-07-20 19:51 ` sashiko-bot
2026-07-30 16:27 ` Farhan Ali [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=01d69d29-e20d-48f7-b4fd-d6a88cd64cc9@linux.ibm.com \
--to=alifm@linux.ibm.com \
--cc=alex@shazbot.org \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=schnelle@linux.ibm.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