From: Bjorn Helgaas <bhelgaas@google.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kees Cook <keescook@chromium.org>,
Colin Ian King <colin.king@canonical.com>,
Betty Dall <betty.dall@hp.com>,
Yijing Wang <wangyijing@huawei.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] PCI updates for v3.8
Date: Tue, 22 Jan 2013 15:56:57 -0700 [thread overview]
Message-ID: <20130122225657.GA14800@google.com> (raw)
Hi Linus,
Here are some more fixes for v3.8. The most important is a fix for a
pciehp deadlock that occurs when unplugging a Thunderbolt adapter. We also
applied the same fix to shpchp, removed CONFIG_EXPERIMENTAL dependencies,
fixed a pcie_aspm=force problem, and fixed a refcount leak.
Bjorn
The following changes since commit d1c3ed669a2d452cacfb48c2d171a1f364dae2ed:
Linux 3.8-rc2 (2013-01-02 18:13:21 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/3.8-pci-fixes-2
for you to fetch changes up to 444ee9bd3d0fa78317c6127c961af5accf50038b:
PCI: remove depends on CONFIG_EXPERIMENTAL (2013-01-17 16:22:05 -0700)
----------------------------------------------------------------
PCI updates for v3.8:
Hotplug
PCI: pciehp: Use per-slot workqueues to avoid deadlock
PCI: shpchp: Make shpchp_wq non-ordered
PCI: shpchp: Handle push button event asynchronously
PCI: shpchp: Use per-slot workqueues to avoid deadlock
Power management
PCI: Allow pcie_aspm=force even when FADT indicates it is unsupported
Misc
PCI/AER: pci_get_domain_bus_and_slot() call missing required pci_dev_put()
PCI: remove depends on CONFIG_EXPERIMENTAL
----------------------------------------------------------------
Betty Dall (1):
PCI/AER: pci_get_domain_bus_and_slot() call missing required pci_dev_put()
Bjorn Helgaas (4):
PCI: shpchp: Make shpchp_wq non-ordered
PCI: shpchp: Handle push button event asynchronously
PCI: shpchp: Use per-slot workqueues to avoid deadlock
Merge branch 'pci/yijing-hotplug-workqueues' into for-linus
Colin Ian King (1):
PCI: Allow pcie_aspm=force even when FADT indicates it is unsupported
Kees Cook (1):
PCI: remove depends on CONFIG_EXPERIMENTAL
Yijing Wang (1):
PCI: pciehp: Use per-slot workqueues to avoid deadlock
drivers/pci/hotplug/pciehp.h | 2 +-
drivers/pci/hotplug/pciehp_core.c | 11 ++---------
drivers/pci/hotplug/pciehp_ctrl.c | 8 ++++----
drivers/pci/hotplug/pciehp_hpc.c | 11 ++++++++++-
drivers/pci/hotplug/shpchp.h | 3 +--
drivers/pci/hotplug/shpchp_core.c | 36 ++++++++++++++----------------------
drivers/pci/hotplug/shpchp_ctrl.c | 6 +++---
drivers/pci/pcie/Kconfig | 2 +-
drivers/pci/pcie/aer/aerdrv_core.c | 1 +
drivers/pci/pcie/aspm.c | 3 +++
10 files changed, 40 insertions(+), 43 deletions(-)
next reply other threads:[~2013-01-22 22:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 22:56 Bjorn Helgaas [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-02 18:48 [GIT PULL] PCI updates for v3.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=20130122225657.GA14800@google.com \
--to=bhelgaas@google.com \
--cc=betty.dall@hp.com \
--cc=colin.king@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=wangyijing@huawei.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).