Commit 8d077c3c authored by Bjorn Helgaas's avatar Bjorn Helgaas

PCI/AER: Factor message prefixes with dev_fmt()

Define dev_fmt() with the common prefix of log messages so we don't have to
repeat it in every printk.  No functional change intended.

Link: https://lore.kernel.org/r/20191213225709.GA213811@google.comSigned-off-by: default avatarBjorn Helgaas <bhelgaas@google.com>
parent 01daacfb
...@@ -10,6 +10,8 @@ ...@@ -10,6 +10,8 @@
* Zhang Yanmin (yanmin.zhang@intel.com) * Zhang Yanmin (yanmin.zhang@intel.com)
*/ */
#define dev_fmt(fmt) "AER: " fmt
#include <linux/pci.h> #include <linux/pci.h>
#include <linux/module.h> #include <linux/module.h>
#include <linux/kernel.h> #include <linux/kernel.h>
...@@ -63,7 +65,7 @@ static int report_error_detected(struct pci_dev *dev, ...@@ -63,7 +65,7 @@ static int report_error_detected(struct pci_dev *dev,
*/ */
if (dev->hdr_type != PCI_HEADER_TYPE_BRIDGE) { if (dev->hdr_type != PCI_HEADER_TYPE_BRIDGE) {
vote = PCI_ERS_RESULT_NO_AER_DRIVER; vote = PCI_ERS_RESULT_NO_AER_DRIVER;
pci_info(dev, "AER: Can't recover (no error_detected callback)\n"); pci_info(dev, "can't recover (no error_detected callback)\n");
} else { } else {
vote = PCI_ERS_RESULT_NONE; vote = PCI_ERS_RESULT_NONE;
} }
...@@ -235,12 +237,12 @@ void pcie_do_recovery(struct pci_dev *dev, enum pci_channel_state state, ...@@ -235,12 +237,12 @@ void pcie_do_recovery(struct pci_dev *dev, enum pci_channel_state state,
pci_aer_clear_device_status(dev); pci_aer_clear_device_status(dev);
pci_cleanup_aer_uncorrect_error_status(dev); pci_cleanup_aer_uncorrect_error_status(dev);
pci_info(dev, "AER: Device recovery successful\n"); pci_info(dev, "device recovery successful\n");
return; return;
failed: failed:
pci_uevent_ers(dev, PCI_ERS_RESULT_DISCONNECT); pci_uevent_ers(dev, PCI_ERS_RESULT_DISCONNECT);
/* TODO: Should kernel panic here? */ /* TODO: Should kernel panic here? */
pci_info(dev, "AER: Device recovery failed\n"); pci_info(dev, "device recovery failed\n");
} }
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment