From: Frederick Lawler <fred@fredlawl.com>
To: bhelgaas@google.com
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
mika.westerberg@linux.intel.com, lukas@wunner.de,
andriy.shevchenko@linux.intel.com, keith.busch@intel.com,
mr.nuke.me@gmail.com, liudongdong3@huawei.com,
thesven73@gmail.com, Frederick Lawler <fred@fredlawl.com>
Subject: [PATCH v2 0/9] PCI: Use PCIe service name in dmesg logs
Date: Thu, 2 May 2019 22:59:37 -0500 [thread overview]
Message-ID: <20190503035946.23608-1-fred@fredlawl.com> (raw)
In referrence to [1], PCIe services did not have uniform logging via pci_*()
printk wrappers. Add dev_fmt() to each service, clean up dmesg logs,
use pci_dbg() for hotplug debug messages, and lastly, uniformally
add Slot(%s) prefixes to hotplug ctrl_*() wrappers.
1. https://lore.kernel.org/linux-pci/20190308180149.GD214730@google.com/
Changes from v1:
- Split dev_fmt() additions into own patches per service
- Kept ctrl_*() wrappers and applied "Slot(%s)" prefix to messages
- Attempted to leave no log gaps between patches
Frederick Lawler (9):
PCI/AER: Cleanup dmesg logs
PCI/DPC: Prefix dmesg logs with PCIe service name
PCI/PME: Prefix dmesg logs with PCIe service name
PCI/LINK: Prefix dmesg logs with PCIe service name
PCI/AER: Prefix dmesg logs with PCIe service name
PCI: hotplug: Prefix dmesg logs with PCIe service name
PCI: hotplug: Prefer CONFIG_DYNAMIC_DEBUG/DEBUG for dmesg logs
PCI: hotplug: Remove unnecessary dbg/err/info/warn() printk() wrappers
PCI: hotplug: Prefix ctrl_*() dmesg logs with pciehp slot name
drivers/pci/hotplug/pciehp.h | 28 ++++----------
drivers/pci/hotplug/pciehp_core.c | 20 ++++++----
drivers/pci/hotplug/pciehp_ctrl.c | 60 ++++++++++++------------------
drivers/pci/hotplug/pciehp_hpc.c | 9 +++--
drivers/pci/hotplug/pciehp_pci.c | 2 +
drivers/pci/pcie/aer.c | 19 ++++++----
drivers/pci/pcie/aer_inject.c | 6 ++-
drivers/pci/pcie/bw_notification.c | 2 +
drivers/pci/pcie/dpc.c | 37 +++++++++---------
drivers/pci/pcie/pme.c | 2 +
10 files changed, 89 insertions(+), 96 deletions(-)
--
2.17.1
next reply other threads:[~2019-05-03 4:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 3:59 Frederick Lawler [this message]
2019-05-03 3:59 ` [PATCH v2 1/9] PCI/AER: Cleanup dmesg logs Frederick Lawler
2019-05-03 19:31 ` Bjorn Helgaas
2019-05-06 8:22 ` Andy Shevchenko
2019-05-03 3:59 ` [PATCH v2 2/9] PCI/DPC: Prefix dmesg logs with PCIe service name Frederick Lawler
2019-05-03 16:44 ` Keith Busch
2019-05-03 19:44 ` Bjorn Helgaas
2019-05-03 3:59 ` [PATCH v2 3/9] PCI/PME: " Frederick Lawler
2019-05-03 19:55 ` Bjorn Helgaas
2019-05-03 3:59 ` [PATCH v2 4/9] PCI/LINK: " Frederick Lawler
2019-05-09 14:12 ` Bjorn Helgaas
2019-05-03 3:59 ` [PATCH v2 5/9] PCI/AER: " Frederick Lawler
2019-05-03 3:59 ` [PATCH v2 6/9] PCI: hotplug: " Frederick Lawler
2019-05-03 20:04 ` Bjorn Helgaas
2019-05-06 8:29 ` Andy Shevchenko
2019-05-03 3:59 ` [PATCH v2 7/9] PCI: hotplug: Prefer CONFIG_DYNAMIC_DEBUG/DEBUG for dmesg logs Frederick Lawler
2019-05-03 20:48 ` Bjorn Helgaas
2019-05-03 3:59 ` [PATCH v2 8/9] PCI: hotplug: Remove unnecessary dbg/err/info/warn() printk() wrappers Frederick Lawler
2019-05-03 3:59 ` [PATCH v2 9/9] PCI: hotplug: Prefix ctrl_*() dmesg logs with pciehp slot name Frederick Lawler
2019-05-09 14:03 ` 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=20190503035946.23608-1-fred@fredlawl.com \
--to=fred@fredlawl.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liudongdong3@huawei.com \
--cc=lukas@wunner.de \
--cc=mika.westerberg@linux.intel.com \
--cc=mr.nuke.me@gmail.com \
--cc=thesven73@gmail.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).