public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / 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@s-opensource.com>,
	Kan Liang <kan.liang@linux.intel.com>,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] EDAC driver for Jacobsville microserver
Date: Fri, 25 Jan 2019 11:58:58 -0800	[thread overview]
Message-ID: <20190125195902.17109-1-tony.luck@intel.com> (raw)

This driver can share a lot of the code from the Skylake driver. But
instead of turning that driver into a maze of twisty function pointers
as we did to share sb_edac.c across several generations we are taking
a different approach. Splitting out the common code into a source file
that can be linked with each driver (when they are modules) or built in
to kernel if the drivers are built in.

Four patches in the series (only part 3 of interest to general LKML audience)

1) Create new files skx_comm_edac.[ch] with all the common functions and
   #defines.
2) Delete all that common code from skx_edac.c an rename what is left as
   skx_base.c. Update Makefile to build driver from common+base.
3) New CPU model number for Jacobsville.
4) Add new EDAC driver for Jacobsville.

Kan Liang (1):
  x86: intel-family.h: Add Atom Tremont (Jacobsville)

Qiuxu Zhuo (3):
  EDAC, skx_comm_edac: Separate common codes from the skx_edac driver
  EDAC, skx_edac: Delete the duplicated codes
  EDAC, i10nm_edac: Add EDAC driver for Intel 10nm server processors

 arch/x86/include/asm/intel-family.h |    3 +-
 drivers/edac/Kconfig                |   12 +
 drivers/edac/Makefile               |    7 +-
 drivers/edac/i10nm_base.c           |  279 ++++++
 drivers/edac/skx_base.c             |  673 +++++++++++++
 drivers/edac/skx_comm_edac.c        |  693 ++++++++++++++
 drivers/edac/skx_comm_edac.h        |  158 ++++
 drivers/edac/skx_edac.c             | 1358 ---------------------------
 8 files changed, 1823 insertions(+), 1360 deletions(-)
 create mode 100644 drivers/edac/i10nm_base.c
 create mode 100644 drivers/edac/skx_base.c
 create mode 100644 drivers/edac/skx_comm_edac.c
 create mode 100644 drivers/edac/skx_comm_edac.h
 delete mode 100644 drivers/edac/skx_edac.c

-- 
2.19.1


             reply	other threads:[~2019-01-25 19:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-25 19:58 Tony Luck [this message]
2019-01-25 19:58 ` [PATCH 1/4] EDAC, skx_comm_edac: Separate common codes from the skx_edac driver Tony Luck
2019-01-29 16:09   ` Borislav Petkov
2019-01-25 19:59 ` [PATCH 2/4] EDAC, skx_edac: Delete the duplicated codes Tony Luck
2019-01-29 17:12   ` Borislav Petkov
2019-01-25 19:59 ` [PATCH 3/4] x86: intel-family.h: Add Atom Tremont (Jacobsville) Tony Luck
2019-01-29 15:48   ` [tip:x86/urgent] x86/cpu: " tip-bot for Kan Liang
2019-01-25 19:59 ` [PATCH 4/4] EDAC, i10nm_edac: Add EDAC driver for Intel 10nm server processors Tony Luck

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=20190125195902.17109-1-tony.luck@intel.com \
    --to=tony.luck@intel.com \
    --cc=aris@redhat.com \
    --cc=bp@alien8.de \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@s-opensource.com \
    --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