nvdimm.lists.linux.dev archive mirror
 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-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: [GIT PULL] libnvdimm for 4.20
Date: Wed, 24 Oct 2018 23:45:54 +0000	[thread overview]
Message-ID: <47580ee876c884c91fdb8c29791257cf715facfa.camel@intel.com> (raw)

Hi Linus, please pull from:

  git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-for-4.20

...to receive the libnvdimm updates for this cycle. No interactions
with other trees this time around. There are updates to the core to
improve driver initialization time, and updates to the 'nfit' driver
for fixing ARS corner cases and exposing some more hardware attributes
to userspace. It has all been in -next for a few releases now with no
reported issues.

---

The following changes since commit 7876320f88802b22d4e2daf7eb027dd14175a0f8:

  Linux 4.19-rc4 (2018-09-16 11:52:37 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-for-4.20

for you to fetch changes up to 594861215c834e4b59a30d4b794f6372717bc197:

  acpi, nfit: Further restrict userspace ARS start requests (2018-10-17 14:02:32 -0700)

----------------------------------------------------------------
libnvdimm for 4.20

* Improve the efficiency and performance of reading nvdimm-namespace
  labels. Reduce the amount of label data read at driver load time by a
  few orders of magnitude. Reduce heavyweight call-outs to
  platform-firmware routines.

* Handle media errors located in the 'struct page' array stored on a
  persistent memory namespace. Let the kernel clear these errors rather
  than an awkward userspace workaround.

* Fix Address Range Scrub (ARS) completion tracking. Correct occasions
  where the kernel indicates completion of ARS before submission.

* Fix asynchronous device registration reference counting.

* Add support for reporting an nvdimm dirty-shutdown-count via sysfs.

* Fix various small libnvdimm core and uapi issues.

----------------------------------------------------------------
Alexander Duyck (7):
      libnvdimm: Hold reference on parent while scheduling async init
      libnvdimm: Set device node in nd_device_register
      nvdimm: Sanity check labeloff
      nvdimm: Clarify comment in sizeof_namespace_index
      nvdimm: Remove empty if statement
      nvdimm: Split label init out from the logic for getting config data
      nvdimm: Use namespace index data to reduce number of label reads needed

Dan Williams (9):
      libnvdimm, region: Fail badblocks listing for inactive regions
      libnvdimm, pmem: Fix badblocks population for 'raw' namespaces
      libnvdimm, dimm: Maximize label transfer size
      libnvdimm, label: Fix sparse warning
      acpi, nfit: Introduce nfit_mem flags
      acpi, nfit: Collect shutdown status
      tools/testing/nvdimm: Populate dirty shutdown data
      acpi, nfit: Fix Address Range Scrub completion tracking
      acpi, nfit: Further restrict userspace ARS start requests

David Howells (2):
      UAPI: ndctl: Fix g++-unsupported initialisation in headers
      UAPI: ndctl: Remove use of PAGE_SIZE

GuangZhe Fu (1):
      libnvdimm, namespace: Drop the repeat assignment for variable dev->parent

Pankaj Gupta (1):
      libnvdimm: remove duplicate include

Vishal Verma (1):
      libnvdimm, pfn: during init, clear errors in the metadata area

 drivers/acpi/nfit/core.c              | 297 +++++++++++++++++++++++-----------
 drivers/acpi/nfit/intel.h             |  38 +++++
 drivers/acpi/nfit/nfit.h              |  21 ++-
 drivers/nvdimm/bus.c                  |  20 ++-
 drivers/nvdimm/dimm.c                 |   6 +-
 drivers/nvdimm/dimm_devs.c            |  60 +++----
 drivers/nvdimm/label.c                | 144 ++++++++++++++++-
 drivers/nvdimm/label.h                |   4 +-
 drivers/nvdimm/namespace_devs.c       |   1 -
 drivers/nvdimm/nd-core.h              |   1 -
 drivers/nvdimm/nd.h                   |   2 +
 drivers/nvdimm/pfn_devs.c             |  61 ++++++-
 drivers/nvdimm/pmem.c                 |   4 +-
 drivers/nvdimm/region_devs.c          |  11 +-
 include/linux/ndctl.h                 |  22 +++
 include/uapi/linux/ndctl.h            |  52 +++---
 tools/testing/nvdimm/Kbuild           |   1 +
 tools/testing/nvdimm/acpi_nfit_test.c |   8 +
 tools/testing/nvdimm/test/nfit.c      |   4 +-
 tools/testing/nvdimm/test/nfit_test.h |  24 ---
 20 files changed, 564 insertions(+), 217 deletions(-)
 create mode 100644 drivers/acpi/nfit/intel.h
 create mode 100644 include/linux/ndctl.h
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

                 reply	other threads:[~2018-10-24 23:45 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=47580ee876c884c91fdb8c29791257cf715facfa.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;
as well as URLs for NNTP newsgroup(s).