From: Bjorn Helgaas <bhelgaas@google.com>
To: linux-pci@vger.kernel.org,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: Lukas Wunner <lukas@wunner.de>, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/9] PCI: Tidy up messages
Date: Mon, 21 Nov 2016 15:45:11 -0600 [thread overview]
Message-ID: <20161121214006.21036.11599.stgit@bhelgaas-glaptop.roam.corp.google.com> (raw)
Remove a few messages that don't contain any useful information, e.g.,
pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp 0000:80:02.0:pcie04: service driver pciehp loaded
pciehp: PCI Express Hot Plug Controller Driver version: 0.4
NOTE: I added a patch to drop Root Complex Event Collector PME support. I
suspect that we really want to keep that, but it looks like it's currently
broken. I would welcome opinions and some help to test it if we fix the
current breakage.
Changes from v1->v2:
- Drop Root Complex Event Collector PME support
- Add PME IRQ to existing log message
- Log PME message once per hierarchy, not once per device
- Log AER probe errors with plain PCI device, not PCIe service device
- Add new AER claim message, including IRQ
- Remove unused AER version macros
---
Bjorn Helgaas (9):
PCI/PME: Drop unused support for PMEs from Root Complex Event Collectors
PCI/PME: Log PME IRQ when claiming Root Port
PCI/AER: Remove unused version macros
PCI/AER: Log errors with PCI device, not PCIe service device
PCI/AER: Log AER IRQ when claiming Root Port
PCI: Remove service driver load/unload messages
PCI: hotplug: Remove hotplug core message
PCI: pciehp: Remove loading message
PCI: Expand "VPD access disabled" quirk message
drivers/pci/hotplug/pci_hotplug_core.c | 10 +++-------
drivers/pci/hotplug/pciehp_core.c | 9 ++++-----
drivers/pci/pcie/aer/aerdrv.c | 18 ++++++------------
drivers/pci/pcie/pme.c | 29 +++++++----------------------
drivers/pci/pcie/portdrv_core.c | 3 ---
drivers/pci/quirks.c | 2 +-
6 files changed, 21 insertions(+), 50 deletions(-)
next reply other threads:[~2016-11-21 21:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 21:45 Bjorn Helgaas [this message]
2016-11-21 21:45 ` [PATCH v2 1/9] PCI/PME: Drop unused support for PMEs from Root Complex Event Collectors Bjorn Helgaas
2016-11-21 22:28 ` Rafael J. Wysocki
2016-11-21 22:42 ` Bjorn Helgaas
2016-11-21 22:58 ` Rafael J. Wysocki
2016-11-21 23:00 ` Bjorn Helgaas
2016-11-21 21:45 ` [PATCH v2 2/9] PCI/PME: Log PME IRQ when claiming Root Port Bjorn Helgaas
2016-11-21 22:29 ` Rafael J. Wysocki
2016-11-21 21:45 ` [PATCH v2 3/9] PCI/AER: Remove unused version macros Bjorn Helgaas
2016-11-21 21:45 ` [PATCH v2 4/9] PCI/AER: Log errors with PCI device, not PCIe service device Bjorn Helgaas
2016-11-21 21:45 ` [PATCH v2 5/9] PCI/AER: Log AER IRQ when claiming Root Port Bjorn Helgaas
2016-11-21 21:45 ` [PATCH v2 6/9] PCI: Remove service driver load/unload messages Bjorn Helgaas
2016-11-21 21:46 ` [PATCH v2 7/9] PCI: hotplug: Remove hotplug core message Bjorn Helgaas
2016-11-21 21:46 ` [PATCH v2 8/9] PCI: pciehp: Remove loading message Bjorn Helgaas
2016-11-21 21:46 ` [PATCH v2 9/9] PCI: Expand "VPD access disabled" quirk message Bjorn Helgaas
2016-11-23 17:36 ` [PATCH v2 0/9] PCI: Tidy up messages 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=20161121214006.21036.11599.stgit@bhelgaas-glaptop.roam.corp.google.com \
--to=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=rafael.j.wysocki@intel.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
all inboxes | Powered by JetHome®