From: skunberg.kelsey at gmail.com (Kelsey Skunberg)
Subject: [Linux-kernel-mentees] [PATCH 0/2] lspci: Add lspci support to decode AIDA64 and dmesg log files
Date: Wed, 3 Jul 2019 18:08:17 -0600 [thread overview]
Message-ID: <20190704000819.25050-1-skunberg.kelsey@gmail.com> (raw)
Add lspci support to decode AIDA64 log files and dmesg log files with
"pci=earlydump" parameter to output PCI configuration space information.
Patch 1: Add lspci support to decode AIDA64 log file.
AIDA64 log file included in patch for testing. Use the following
command to run:
lspci -F tests/aida64-dump
Patch 2: Add lspci support to decode dmesg log file with
"pci=earlydump" parameter.
dmesg log file with "pci=earlydump" included in patch for
testing. Use the following command to run:
lspci -F tests/dmesg-dump
Bjorn Helgaas (2):
lspci: Add lspci support to decode an AIDA64 log file
lspci: Add lspci support to decode "pci=earlydump" output
lib/dump.c | 96 ++-
tests/aida64-dump | 954 ++++++++++++++++++++++++
tests/dmesg-dump | 1795 +++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 2812 insertions(+), 33 deletions(-)
create mode 100644 tests/aida64-dump
create mode 100644 tests/dmesg-dump
--
2.20.1
WARNING: multiple messages have this Message-ID (diff)
From: skunberg.kelsey@gmail.com (Kelsey Skunberg)
Subject: [Linux-kernel-mentees] [PATCH 0/2] lspci: Add lspci support to decode AIDA64 and dmesg log files
Date: Wed, 3 Jul 2019 18:08:17 -0600 [thread overview]
Message-ID: <20190704000819.25050-1-skunberg.kelsey@gmail.com> (raw)
Message-ID: <20190704000817._zUxMUUqoxClx_XFDiYzpcVdsYLdLchmVHdmcO_sark@z> (raw)
Add lspci support to decode AIDA64 log files and dmesg log files with
"pci=earlydump" parameter to output PCI configuration space information.
Patch 1: Add lspci support to decode AIDA64 log file.
AIDA64 log file included in patch for testing. Use the following
command to run:
lspci -F tests/aida64-dump
Patch 2: Add lspci support to decode dmesg log file with
"pci=earlydump" parameter.
dmesg log file with "pci=earlydump" included in patch for
testing. Use the following command to run:
lspci -F tests/dmesg-dump
Bjorn Helgaas (2):
lspci: Add lspci support to decode an AIDA64 log file
lspci: Add lspci support to decode "pci=earlydump" output
lib/dump.c | 96 ++-
tests/aida64-dump | 954 ++++++++++++++++++++++++
tests/dmesg-dump | 1795 +++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 2812 insertions(+), 33 deletions(-)
create mode 100644 tests/aida64-dump
create mode 100644 tests/dmesg-dump
--
2.20.1
next reply other threads:[~2019-07-04 0:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 0:08 skunberg.kelsey [this message]
2019-07-04 0:08 ` [Linux-kernel-mentees] [PATCH 0/2] lspci: Add lspci support to decode AIDA64 and dmesg log files Kelsey Skunberg
2019-07-04 0:08 ` [Linux-kernel-mentees] [PATCH 1/2] lspci: Add lspci support to decode an AIDA64 log file skunberg.kelsey
2019-07-04 0:08 ` Kelsey Skunberg
2019-07-04 0:08 ` [Linux-kernel-mentees] [PATCH 2/2] lspci: Add lspci support to decode "pci=earlydump" output skunberg.kelsey
2019-07-04 0:08 ` Kelsey Skunberg
2020-01-21 21:00 ` [Linux-kernel-mentees] [PATCH 0/2] lspci: Add lspci support to decode AIDA64 and dmesg log files Martin Mareš
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=20190704000819.25050-1-skunberg.kelsey@gmail.com \
--to=linux-kernel-mentees@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).