mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: linux-nvdimm@ml01.01.org
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: [PATCH 0/3] ACPI 6.1 NFIT Compatibility
Date: Mon, 08 Feb 2016 10:30:53 -0800	[thread overview]
Message-ID: <20160208183052.27820.68922.stgit@dwillia2-desk3.amr.corp.intel.com> (raw)

The latest NFIT specification clarifies that a memory device will have a
control region table per function interface.  Without the fix in [PATCH
1/3] Linux will miscount the number of DIMMs and fail to load the
driver.  The fix is tagged for -stable on the expectation that ACPI 6.1
compatible systems will overlap current -stable development branches.

The latter two patches in the series are verification tests that can be
integrated for 4.6.

---

Dan Williams (3):
      nfit: fix multi-interface dimm handling, acpi6.1 compatibility
      nfit, tools/testing/nvdimm: add format interface code definitions
      nfit, tools/testing/nvdimm: test multiple control regions per-dimm


 drivers/acpi/nfit.c              |   71 +++++++++++-----------
 drivers/acpi/nfit.h              |    6 ++
 tools/testing/nvdimm/test/nfit.c |  125 ++++++++++++++++++++++++++++++--------
 3 files changed, 141 insertions(+), 61 deletions(-)

             reply	other threads:[~2016-02-08 18:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 18:30 Dan Williams [this message]
2016-02-08 18:30 ` [PATCH 1/3] nfit: fix multi-interface dimm handling, acpi6.1 compatibility Dan Williams
2016-02-08 19:10   ` Linda Knippers
2016-02-08 20:23     ` Linda Knippers
2016-02-08 20:37       ` Dan Williams
2016-02-08 18:31 ` [PATCH 2/3] nfit, tools/testing/nvdimm: add format interface code definitions Dan Williams
2016-02-08 18:31 ` [PATCH 3/3] nfit, tools/testing/nvdimm: test multiple control regions per-dimm Dan Williams

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=20160208183052.27820.68922.stgit@dwillia2-desk3.amr.corp.intel.com \
    --to=dan.j.williams@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@ml01.01.org \
    --cc=stable@vger.kernel.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

all inboxes | Powered by JetHome®