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>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Paul Menzel <pmenzel@molgen.mpg.de>,
Prarit Bhargava <prarit@redhat.com>,
Myron Stowe <myron.stowe@redhat.com>
Subject: [GIT PULL] PCI fixes for v4.8
Date: Wed, 14 Sep 2016 15:11:24 -0500 [thread overview]
Message-ID: <20160914201124.GA12386@localhost> (raw)
Hi Linus,
Here are two changes for v4.8. The first fixes a "[Firmware Bug]: reg
0x10: invalid BAR (can't size)" warning on Haswell, and the second fixes a
problem in some new runtime suspend functionality we merged for v4.8.
Bjorn
The following changes since commit 21c80c9fefc3db10b530a96eb0478c29eb28bf77:
x86/PCI: VMD: Fix infinite loop executing irq's (2016-08-23 16:36:42 -0500)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-v4.8-fixes-2
for you to fetch changes up to 035ee288ae7ade4152f1c3cf23a587b04fdc526c:
PCI: Fix bridge_d3 update on device removal (2016-09-13 16:00:18 -0500)
----------------------------------------------------------------
PCI updates for v4.8:
Enumeration
Mark Haswell Power Control Unit as having non-compliant BARs (Bjorn Helgaas)
Power management
Fix bridge_d3 update on device removal (Lukas Wunner)
----------------------------------------------------------------
Bjorn Helgaas (1):
PCI: Mark Haswell Power Control Unit as having non-compliant BARs
Lukas Wunner (1):
PCI: Fix bridge_d3 update on device removal
arch/x86/pci/fixup.c | 20 +++++++++++++-------
drivers/pci/remove.c | 3 +--
2 files changed, 14 insertions(+), 9 deletions(-)
next reply other threads:[~2016-09-14 20:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 20:11 Bjorn Helgaas [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-25 13:29 [GIT PULL] PCI fixes for v4.8 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=20160914201124.GA12386@localhost \
--to=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mika.westerberg@linux.intel.com \
--cc=myron.stowe@redhat.com \
--cc=pmenzel@molgen.mpg.de \
--cc=prarit@redhat.com \
--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).