Re: [PATCH v1 0/2] PCI/AER: Clean up minor logging issues

2018-06-05 Thread Bjorn Helgaas
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

Re: [PATCH v1 0/2] PCI/AER: Clean up minor logging issues

2018-06-05 Thread Bjorn Helgaas
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

[PATCH v1 0/2] PCI/AER: Clean up minor logging issues

2018-05-30 Thread Bjorn Helgaas
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

[PATCH v1 0/2] PCI/AER: Clean up minor logging issues

2018-05-30 Thread Bjorn Helgaas
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