From: Bjorn Helgaas <bhelgaas@google.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Chao Zhou <chao.zhou@intel.com>, Joerg Roedel <joro@8bytes.org>,
Yinghai Lu <yinghai@kernel.org>
Subject: [GIT PULL] PCI fixes for v3.18
Date: Thu, 6 Nov 2014 11:54:53 -0700 [thread overview]
Message-ID: <20141106185453.GA17929@google.com> (raw)
Hi Linus,
This fixes an oops when enabling SR-IOV VF devices. The oops is a
regression I added by configuring all devices during enumeration.
Bjorn
The following changes since commit d8e7d53a2fc14e0830ab728cb84ee19933d3ac8d:
PCI: Rename sysfs 'enabled' file back to 'enable' (2014-10-30 11:17:10 -0600)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-v3.18-fixes-2
for you to fetch changes up to 32f638fc11db0526c706454d9ab4339d55ac89f3:
PCI: Don't oops on virtual buses in acpi_pci_get_bridge_handle() (2014-11-05 13:06:16 -0700)
----------------------------------------------------------------
PCI update for v3.18:
Enumeration
- Don't oops on virtual buses in acpi_pci_get_bridge_handle() (Yinghai Lu)
----------------------------------------------------------------
Yinghai Lu (1):
PCI: Don't oops on virtual buses in acpi_pci_get_bridge_handle()
include/linux/pci-acpi.h | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
next reply other threads:[~2014-11-06 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 18:54 Bjorn Helgaas [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-03 18:30 [GIT PULL] PCI fixes for v3.18 Bjorn Helgaas
[not found] <20141120194422.GA6923@google.com>
2014-11-20 21:10 ` Bjorn Helgaas
2014-10-31 16:54 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=20141106185453.GA17929@google.com \
--to=bhelgaas@google.com \
--cc=chao.zhou@intel.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.