[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Vfk0gftuSMQBzZUgoeBPLeUOUkcdKJFbXKq3-joDgT0fw@mail.gmail.com>
Date: Thu, 9 May 2019 20:42:10 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: Frederick Lawler <fred@...dlawl.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Lukas Wunner <lukas@...ner.de>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Keith Busch <keith.busch@...el.com>,
Dongdong Liu <liudongdong3@...wei.com>,
Sven Van Asbroeck <thesven73@...il.com>,
linux-pci@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>
Subject: Re: [PATCH 04/10] PCI/AER: Log messages with pci_dev, not pcie_device
On Thu, May 9, 2019 at 5:19 PM Bjorn Helgaas <helgaas@...nel.org> wrote:
> Log messages with pci_dev, not pcie_device. Factor out common message
> prefixes with dev_fmt().
>
> Example output change:
>
> - aer 0000:00:00.0:pci002: AER enabled with IRQ ...
> + pcieport 0000:00:00.0: AER: enabled with IRQ ...
> + pci_err(port, "request AER IRQ %d failed\n",
> dev->irq);
Possible to be on one line?
> + pci_warn(edev->port,
> + "AER service is not initialized\n");
checkpatch won't complain if it would be on one line.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists