From: Tony Luck <tony.luck@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Tony Luck <tony.luck@intel.com>,
Qiuxu Zhuo <qiuxu.zhuo@intel.com>,
Aristeu Rozanski <aris@redhat.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-edac@vger.kernel.org
Subject: [PATCH 0/2] EDAC, skx: Provide more machine specific location detail
Date: Fri, 13 Sep 2019 15:13:42 -0700 [thread overview]
Message-ID: <20190913221344.13055-1-tony.luck@intel.com> (raw)
First patch refactors code so that second can work on systems
with and without the ACPI ADXL address translation code. Perhaps
has some value on its own as the code is, IMHO, a little cleaner.
Second is in RFC state. Im looking for input on whether to just print
the extra information to the console log (as the patch does now) or
whether to tag it onto the long string that we push though the EDAC
reporting path.
Tony Luck (2):
EDAC, skx_common: Refactor so that we initialize "dev" in result of
adxl decode.
EDAC, skx: Retrieve and print retry_rd_err_log registers
drivers/edac/skx_base.c | 38 +++++++++++++++++++++++++--
drivers/edac/skx_common.c | 55 +++++++++++++++++++++------------------
drivers/edac/skx_common.h | 4 ++-
3 files changed, 68 insertions(+), 29 deletions(-)
--
2.20.1
next reply other threads:[~2019-09-13 22:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 22:13 Tony Luck [this message]
2019-09-13 22:13 ` [PATCH 1/2] EDAC, skx_common: Refactor so that we initialize "dev" in result of adxl decode Tony Luck
2019-09-18 10:40 ` Mauro Carvalho Chehab
2019-09-23 23:36 ` Luck, Tony
2019-09-13 22:13 ` [RFC PATCH 2/2] EDAC, skx: Retrieve and print retry_rd_err_log registers Tony Luck
2019-09-18 10:52 ` Mauro Carvalho Chehab
2019-09-23 23:57 ` Luck, Tony
2019-09-24 21:52 ` [PATCHv2 " Tony Luck
2019-09-17 20:05 ` [PATCH 0/2] EDAC, skx: Provide more machine specific location detail Aristeu Rozanski
2019-09-18 10:30 ` Mauro Carvalho Chehab
2019-09-25 13:51 ` Aristeu Rozanski
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=20190913221344.13055-1-tony.luck@intel.com \
--to=tony.luck@intel.com \
--cc=aris@redhat.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=qiuxu.zhuo@intel.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;
as well as URLs for NNTP newsgroup(s).