From: Bjorn Helgaas <helgaas@kernel.org>
To: linux-pci@vger.kernel.org
Cc: Oza Pawandeep <poza@codeaurora.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] PCI/AER: Clean up minor logging issues
Date: Tue, 5 Jun 2018 17:21:59 -0500 [thread overview]
Message-ID: <20180605222158.GD226399@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <152770259826.80701.7360032106128917833.stgit@bhelgaas-glaptop.roam.corp.google.com>
On Wed, May 30, 2018 at 12:54:10PM -0500, Bjorn Helgaas wrote:
> AER logging printed the plain 16-bit Requester ID straight out of the TLP,
> which is hard to interpret, e.g., id=00e4 corresponds to what we normally
> see as 00:1c.4 in dmesg or lspci.
>
> Also, there's no need to print the vendor/device ID of the root port
> reporting an error; we can easily find that from dmesg or lspci.
>
> ---
>
> Bjorn Helgaas (2):
> PCI/AER: Decode Error Source Requester ID
> PCI/AER: Stop printing vendor/device ID
>
>
> drivers/pci/pcie/aer/aerdrv_errprint.c | 23 +++++++++++++----------
> 1 file changed, 13 insertions(+), 10 deletions(-)
I applied the first but not the second to pci/aer for v4.18.
prev parent reply other threads:[~2018-06-05 22:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 17:54 Bjorn Helgaas
2018-05-30 17:54 ` [PATCH v1 1/2] PCI/AER: Decode Error Source Requester ID Bjorn Helgaas
2018-05-30 18:32 ` Lukas Wunner
2018-05-31 4:54 ` Bjorn Helgaas
2018-05-30 18:41 ` Rajat Jain
2018-05-31 4:42 ` Bjorn Helgaas
2018-05-31 17:35 ` Rajat Jain
2018-05-30 17:54 ` [PATCH v1 2/2] PCI/AER: Stop printing vendor/device ID Bjorn Helgaas
2018-05-30 18:18 ` Rajat Jain
2018-05-31 0:28 ` Bjorn Helgaas
2018-06-05 22: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=20180605222158.GD226399@bhelgaas-glaptop.roam.corp.google.com \
--to=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=poza@codeaurora.org \
/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®