Linux-EDAC Archive on lore.kernel.org
 help / color / Atom feed
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
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


             reply index

Thread overview: 3+ 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-13 22:13 ` [RFC PATCH 2/2] EDAC, skx: Retrieve and print retry_rd_err_log registers Tony Luck

Reply instructions:

You may reply publically 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

Linux-EDAC Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-edac/0 linux-edac/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-edac linux-edac/ https://lore.kernel.org/linux-edac \
		linux-edac@vger.kernel.org linux-edac@archiver.kernel.org
	public-inbox-index linux-edac


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-edac


AGPL code for this site: git clone https://public-inbox.org/ public-inbox