public inbox for linux-nvdimm@lists.01.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Jean Delvare <jdelvare@suse.com>,
	linux-nvdimm@lists.01.org,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Aristeu Rozanski <aris@redhat.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-acpi@vger.kernel.org, Qiuxu Zhuo <qiuxu.zhuo@intel.com>,
	Lv Zheng <lv.zheng@intel.com>,
	linux-edac@vger.kernel.org, Len Brown <lenb@kernel.org>
Subject: Re: [RFC PATCH 3/4] edac: Add new memory type for non-volatile DIMMs
Date: Mon, 4 Dec 2017 16:21:33 -0800	[thread overview]
Message-ID: <20171205002133.2ojkurykvv6zpc4m@agluck-desk> (raw)
In-Reply-To: <20171204223711.4l7gbd7op7yvsrza@pd.tnic>

On Mon, Dec 04, 2017 at 11:37:11PM +0100, Borislav Petkov wrote:
> On Thu, Nov 30, 2017 at 12:40:41PM -0800, Tony Luck wrote:
> WTF, there are *two* string arrays with memory types?! How did that
> happen?
> 
> Can you please remove that above in a prepatch and switch to
> edac_mem_types? Or should we switch to this mem_types array instead and
> kill edac_mem_types since former is visible in sysfs?
> 
> :-( Grrr.

Oops. I didn't stare hard enough as I walked the "grep" output
to just blindly add a new case everywhere for the new type.

Need to resolve the differences:
1) MEM_LRDDR3 only appears in one of the tables
2) edac_mem_types[] is exported from edac_mc.c and used
   by two drivers
3) mem_types[] is static in edac_mc_sysfs.c, but values
   are visible to user via sysfs
4) Strings are different between the two :-(

Since the drivers that use edac_mem_types[] only do so in edac_dbg()
output, I think it's safe to declare those strings as the non-canon
ones.

So the plan: copy the strings from mem_types[] to edac_mem_types[]
and then make edac_mc_sysfs.c pick up the exported list from edac_mc.c
instead of having its own static version.

Both files have the same build scope:

edac_core-y     := edac_mc.o edac_device.o edac_mc_sysfs.o

so there shouldn't be any weird dependency problems.

-Tony
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

  reply	other threads:[~2017-12-05  0:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30 20:40 [RFC PATCH 0/4] Teach EDAC driver about NVDIMMs Tony Luck
2017-11-30 20:40 ` [RFC PATCH 1/4] acpi, nfit: Add function to look up nvdimm device and provide SMBIOS handle Tony Luck
2017-11-30 20:40 ` [RFC PATCH 2/4] firmware: dmi: Add function to look up a handle and return DIMM size Tony Luck
2017-12-04 21:38   ` Borislav Petkov
2017-12-04 22:03     ` Luck, Tony
2017-12-04 22:07       ` Borislav Petkov
2017-11-30 20:40 ` [RFC PATCH 3/4] edac: Add new memory type for non-volatile DIMMs Tony Luck
2017-12-04 22:37   ` Borislav Petkov
2017-12-05  0:21     ` Luck, Tony [this message]
2017-11-30 20:40 ` [RFC PATCH 4/4] EDAC, skx_edac: Detect " Tony Luck
2017-12-05 10:54   ` Borislav Petkov
2017-12-05 20:03     ` Luck, Tony
2017-12-05 21:44       ` Borislav Petkov
2017-12-05 22:24         ` Luck, Tony
2017-12-06 14:55           ` Borislav Petkov

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=20171205002133.2ojkurykvv6zpc4m@agluck-desk \
    --to=tony.luck@intel.com \
    --cc=aris@redhat.com \
    --cc=bp@alien8.de \
    --cc=jdelvare@suse.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=lv.zheng@intel.com \
    --cc=mchehab@kernel.org \
    --cc=qiuxu.zhuo@intel.com \
    --cc=rjw@rjwysocki.net \
    /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