From: Bjorn Helgaas <helgaas@kernel.org>
To: Yicong Yang <yangyicong@hisilicon.com>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org, kw@linux.com,
linuxarm@huawei.com, prime.zeng@huawei.com
Subject: Re: [PATCH v2] PCI/AER: Use consistent format when printing PCI device
Date: Thu, 27 May 2021 18:21:06 -0500 [thread overview]
Message-ID: <20210527232106.GA1443093@bjorn-Precision-5520> (raw)
In-Reply-To: <1617015721-51701-1-git-send-email-yangyicong@hisilicon.com>
On Mon, Mar 29, 2021 at 07:02:01PM +0800, Yicong Yang wrote:
> We use format domain:bus:slot.function when printing
> PCI device. Use consistent format in AER messages.
>
> Reviewed-by: Krzysztof Wilczyński <kw@linux.com>
> Signed-off-by: Yicong Yang <yangyicong@hisilicon.com>
Applied to pci/error for v5.14, thanks!
I also dropped the "AER recover:" prefixes, since pr_fmt() already gives
us an "AER:" prefix.
> ---
> Change since v1:
> - address comments from Krzysztof
> Link: https://lore.kernel.org/linux-pci/1616752057-9720-1-git-send-email-yangyicong@hisilicon.com/
>
> drivers/pci/pcie/aer.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/pcie/aer.c b/drivers/pci/pcie/aer.c
> index ba22388..f7f0ca5 100644
> --- a/drivers/pci/pcie/aer.c
> +++ b/drivers/pci/pcie/aer.c
> @@ -983,7 +983,7 @@ static void aer_recover_work_func(struct work_struct *work)
> pdev = pci_get_domain_bus_and_slot(entry.domain, entry.bus,
> entry.devfn);
> if (!pdev) {
> - pr_err("AER recover: Can not find pci_dev for %04x:%02x:%02x:%x\n",
> + pr_err("AER recover: Can not find pci_dev for %04x:%02x:%02x.%x\n",
> entry.domain, entry.bus,
> PCI_SLOT(entry.devfn), PCI_FUNC(entry.devfn));
> continue;
> @@ -1022,7 +1022,7 @@ void aer_recover_queue(int domain, unsigned int bus, unsigned int devfn,
> &aer_recover_ring_lock))
> schedule_work(&aer_recover_work);
> else
> - pr_err("AER recover: Buffer overflow when recovering AER for %04x:%02x:%02x:%x\n",
> + pr_err("AER recover: Buffer overflow when recovering AER for %04x:%02x:%02x.%x\n",
> domain, bus, PCI_SLOT(devfn), PCI_FUNC(devfn));
> }
> EXPORT_SYMBOL_GPL(aer_recover_queue);
> --
> 2.8.1
>
prev parent reply other threads:[~2021-05-27 23:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 11:02 [PATCH v2] PCI/AER: Use consistent format when printing PCI device Yicong Yang
2021-05-27 23:21 ` Bjorn Helgaas [this message]
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=20210527232106.GA1443093@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=prime.zeng@huawei.com \
--cc=yangyicong@hisilicon.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