From: Bjorn Helgaas <helgaas@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Robert Święcki" <robert@swiecki.net>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: [GIT PULL] PCI fixes for v5.16
Date: Thu, 11 Nov 2021 13:50:40 -0600 [thread overview]
Message-ID: <20211111195040.GA1345641@bhelgaas> (raw)
The following changes since commit dda4b381f05d447a0ae31e2e44aeb35d313a311f:
Merge branch 'remotes/lorenzo/pci/xgene' (2021-11-05 11:28:53 -0500)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git pci-v5.16-fixes-1
for you to fetch changes up to e0217c5ba10d7bf640f038b2feae58e630f2f958:
Revert "PCI: Use to_pci_driver() instead of pci_dev->driver" (2021-11-11 13:36:22 -0600)
N.B.: My for-linus branch, which contains these, also includes a revert of
041284181226 ("of/irq: Allow matching of an interrupt-map local to an
interrupt controller"). That revert is *not* included here and we hope we
don't need it, but that issue is not resolved yet.
----------------------------------------------------------------
PCI fixes:
- Revert conversion to struct device.driver instead of struct
pci_dev.driver. The device.driver is set earlier, and using it
caused the PCI core to call driver PM entry points before .probe()
and after .remove(), when the driver isn't prepared. This caused
NULL pointer dereferences in i2c_designware_pci and probably other
driver issues (Bjorn Helgaas)
----------------------------------------------------------------
Bjorn Helgaas (2):
Revert "PCI: Remove struct pci_dev->driver"
Revert "PCI: Use to_pci_driver() instead of pci_dev->driver"
drivers/pci/iov.c | 24 +++++++++---------------
drivers/pci/pci-driver.c | 37 ++++++++++++++++++++-----------------
drivers/pci/pci.c | 17 ++++++++---------
drivers/pci/pcie/err.c | 8 ++++----
include/linux/pci.h | 1 +
5 files changed, 42 insertions(+), 45 deletions(-)
next reply other threads:[~2021-11-11 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 19:50 Bjorn Helgaas [this message]
2021-11-11 23:23 ` [GIT PULL] PCI fixes for v5.16 pr-tracker-bot
2021-12-10 16:44 Bjorn Helgaas
2021-12-10 19:58 ` pr-tracker-bot
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=20211111195040.GA1345641@bhelgaas \
--to=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rafael@kernel.org \
--cc=robert@swiecki.net \
--cc=torvalds@linux-foundation.org \
--cc=u.kleine-koenig@pengutronix.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 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).