From: Lukas Wunner <lukas@wunner.de>
To: Bjorn Helgaas <helgaas@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Riana Tauro <riana.tauro@intel.com>,
"Sean C. Dardis" <sean.c.dardis@intel.com>,
Farhan Ali <alifm@linux.ibm.com>,
Benjamin Block <bblock@linux.ibm.com>,
Niklas Schnelle <schnelle@linux.ibm.com>,
Alek Du <alek.du@intel.com>,
"Mahesh J Salgaonkar" <mahesh@linux.ibm.com>,
Oliver OHalloran <oohall@gmail.com>,
linuxppc-dev@lists.ozlabs.org, linux-pci@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: [PATCH v2 0/3] PCI: Universal error recoverability of devices
Date: Wed, 19 Nov 2025 09:50:00 +0100 [thread overview]
Message-ID: <cover.1763483367.git.lukas@wunner.de> (raw)
This series intends to replace commit 1dc302f7fccc ("PCI: Ensure error
recoverability at all times") on the pci/err topic branch:
https://git.kernel.org/pci/pci/c/1dc302f7fccc
The commit is assigning "dev->state_saved = false" in pci_bus_add_device()
and during review there were requests to explain the assignment more
clearly in a code comment.
However the assignment is (only) necessitated by missing assignments in
pci_legacy_suspend() and pci_pm_freeze(), so I propose to instead add
*those* assignments (patch [1/3]) and thus avoid the need for the
assignment in pci_bus_add_device(), together with its code comment.
Furthermore the commit is *removing* an assignment in pci_device_add().
I am separating that out to new patch [2/3].
So patch [3/3] is identical to the commit, but without the addition
of an assignment in pci_bus_add_device() and without the removal
of an assignment in pci_device_add().
I am looking into improving the documentation on pci_save_state()
in a separate series.
Lukas Wunner (3):
PCI/PM: Reinstate clearing state_saved in legacy and !pm codepaths
PCI/PM: Stop needlessly clearing state_saved on enumeration and thaw
PCI/ERR: Ensure error recoverability at all times
drivers/pci/bus.c | 3 +++
drivers/pci/pci-driver.c | 6 ++++--
drivers/pci/pci.c | 3 ---
drivers/pci/probe.c | 2 --
4 files changed, 7 insertions(+), 7 deletions(-)
--
2.51.0
next reply other threads:[~2025-11-19 8:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 8:50 Lukas Wunner [this message]
2025-11-19 8:50 ` [PATCH v2 1/3] PCI/PM: Reinstate clearing state_saved in legacy and !pm codepaths Lukas Wunner
2025-11-19 21:08 ` Rafael J. Wysocki
2025-11-25 23:18 ` Bjorn Helgaas
2025-11-26 12:49 ` Lukas Wunner
2025-11-26 23:46 ` Bjorn Helgaas
2025-11-27 7:58 ` Lukas Wunner
2025-11-27 12:51 ` Rafael J. Wysocki
2025-11-19 8:50 ` [PATCH v2 2/3] PCI/PM: Stop needlessly clearing state_saved on enumeration and thaw Lukas Wunner
2025-11-19 21:09 ` Rafael J. Wysocki
2025-11-19 8:50 ` [PATCH v2 3/3] PCI/ERR: Ensure error recoverability at all times Lukas Wunner
2025-11-25 21:03 ` [PATCH v2 0/3] PCI: Universal error recoverability of devices Bjorn Helgaas
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=cover.1763483367.git.lukas@wunner.de \
--to=lukas@wunner.de \
--cc=alek.du@intel.com \
--cc=alifm@linux.ibm.com \
--cc=bblock@linux.ibm.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=oohall@gmail.com \
--cc=rafael@kernel.org \
--cc=riana.tauro@intel.com \
--cc=schnelle@linux.ibm.com \
--cc=sean.c.dardis@intel.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;
as well as URLs for NNTP newsgroup(s).