public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Williams, Dan J" <dan.j.williams@intel.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: [GIT PULL] libnvdimm fixes for 4.17-rc2
Date: Sun, 22 Apr 2018 00:17:25 +0000	[thread overview]
Message-ID: <1524356236.26036.13.camel@intel.com> (raw)

Hi Linus, please pull from

  git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes

...to receive, a regression fix, new unit test infrastructure and a
build fix.

* The regression fix addresses support for the new NVDIMM label storage
area access commands (_LSI, _LSR, and _LSW). The Intel specific version
of these commands communicated the "Device Locked" status on the label-
storage-information command. However, these new commands (standardized
in ACPI 6.2) communicate the "Device Locked" status on the label-
storage-read command, and the driver was missing the indication.
Reading from locked persistent memory is similar to reading unmapped
PCI memory space, returns all 1's.

* Unit test infrastructure is added to regression test the "Device
Locked" detection failure.

* A build fix is included to allow the "of_pmem" driver to be built as
a module and translate an Open Firmware described device to its local
numa node.

---

The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:

  Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes

for you to fetch changes up to c5794510d7b5f210f05531ff9e82432cf7244367:

  MAINTAINERS: Add backup maintainers for libnvdimm and DAX (2018-04-19 15:22:50 -0700)

----------------------------------------------------------------
Dan Williams (6):
      libnvdimm, dimm: handle EACCES failures from label reads
      tools/testing/nvdimm: allow custom error code injection
      tools/testing/nvdimm: support nfit_test_dimm attributes under nfit_test.1
      tools/testing/nvdimm: fix missing newline in nfit_test_dimm 'handle' attribute
      tools/testing/nvdimm: enable labels for nfit_test.1 dimms
      Revert "libnvdimm, of_pmem: workaround OF_NUMA=n build error"

Dave Jiang (2):
      device-dax: allow MAP_SYNC to succeed
      MAINTAINERS: Add backup maintainers for libnvdimm and DAX

Rob Herring (1):
      libnvdimm, of_pmem: use dev_to_node() instead of of_node_to_nid()

 MAINTAINERS                      | 15 +++++++
 drivers/dax/device.c             |  2 +
 drivers/nvdimm/Kconfig           |  3 +-
 drivers/nvdimm/dimm_devs.c       | 22 ++++++-----
 drivers/nvdimm/of_pmem.c         |  2 +-
 tools/testing/nvdimm/test/nfit.c | 84 +++++++++++++++++++++++++++++++---------
 6 files changed, 96 insertions(+), 32 deletions(-)

                 reply	other threads:[~2018-04-22  0:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1524356236.26036.13.camel@intel.com \
    --to=dan.j.williams@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=torvalds@linux-foundation.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