From: Bjorn Helgaas <helgaas@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Wunner <lukas@wunner.de>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Alan Stern <stern@rowland.harvard.edu>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: [GIT PULL] PCI fixes for v4.6
Date: Tue, 10 May 2016 12:28:03 -0500 [thread overview]
Message-ID: <20160510172803.GA4325@localhost> (raw)
Hi Linus,
Since v4.5, we've WARNed during resume if a PCI device, including a
Thunderbolt device, was added while we were suspended. A change we merged
for v4.6-rc1 turned that warning into a system hang. These patches from
Lukas fix this issue.
Bjorn
The following changes since commit 67e658794ca191b3221b143f2a1c10d002c40bc8:
cxgb4: Set VPD size so we can read both VPD structures (2016-04-15 13:00:18 -0500)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-v4.6-fixes-3
for you to fetch changes up to 9a2a5a638f8eb9c612a7a9af0afab93f506f6ba4:
PCI: Do not treat EPROBE_DEFER as device attach failure (2016-05-02 13:49:11 -0500)
----------------------------------------------------------------
PCI updates for v4.6:
Enumeration
Fix BUG on device attach failure (Lukas Wunner)
Do not treat EPROBE_DEFER as device attach failure (Lukas Wunner)
----------------------------------------------------------------
Lukas Wunner (2):
PCI: Fix BUG on device attach failure
PCI: Do not treat EPROBE_DEFER as device attach failure
drivers/pci/bus.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
next reply other threads:[~2016-05-10 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 17:28 Bjorn Helgaas [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-19 0:06 [GIT PULL] PCI fixes for v4.6 Bjorn Helgaas
2016-03-22 14:32 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=20160510172803.GA4325@localhost \
--to=helgaas@kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=rafael.j.wysocki@intel.com \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.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 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).