linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] libnvdimm for v5.9
Date: Tue, 11 Aug 2020 01:20:48 +0000	[thread overview]
Message-ID: <f44b21c38313fa8e19a3e70eb285e0dd319eb421.camel@intel.com> (raw)

Hi Linus, please pull from:

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

...to receive a new feature in libnvdimm - 'Runtime Firmware
Activation', and a few small cleanups and fixes in libnvdimm and DAX.

You'd normally receive this pull request from Dan Williams, but he's
busy watching a newborn (Congrats Dan!), so I'm watching libnvdimm this
cycle.

I'd originally intended to make separate topic-based pull requests - one
for libnvdimm, and one for DAX, but some of the DAX material fell out
since it wasn't quite ready. I ended up merging the two branches into
one, and hence a couple of 'internal' merges - I hope these are ok. If
you prefer that I should've handled this differently please let me know!

I was also expecting a potential conflict - I was assuming Greg had
pulled in one of Dan's patches[1] through driver-core, but I don't see
it in his tree, and a test merge with the current master went through
cleanly.

There were a small handful of late fixes, but everything has had at
least a week of -next soak time without any reported issues. We've also
received a positive build notification from 0-day.

[1]: https://lore.kernel.org/linux-nvdimm/20200721104442.GF1676612@kroah.com/

---

The following changes since commit 48778464bb7d346b47157d21ffde2af6b2d39110:

  Linux 5.8-rc2 (2020-06-21 15:45:29 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 7f674025d9f7321dea11b802cc0ab3f09cbe51c5:

  libnvdimm/security: ensure sysfs poll thread woke up and fetch updated attr (2020-08-03 18:54:13 -0600)

----------------------------------------------------------------
libnvdimm for 5.9

- Add 'Runtime Firmware Activation' support for NVDIMMs that advertise
  the relevant capability
- Misc libnvdimm and DAX cleanups

----------------------------------------------------------------
Coly Li (1):
      dax: print error message by pr_info() in __generic_fsdax_supported()

Dan Williams (12):
      libnvdimm: Validate command family indices
      ACPI: NFIT: Move bus_dsm_mask out of generic nvdimm_bus_descriptor
      ACPI: NFIT: Define runtime firmware activation commands
      tools/testing/nvdimm: Cleanup dimm index passing
      tools/testing/nvdimm: Add command debug messages
      tools/testing/nvdimm: Prepare nfit_ctl_test() for ND_CMD_CALL emulation
      tools/testing/nvdimm: Emulate firmware activation commands
      driver-core: Introduce DEVICE_ATTR_ADMIN_{RO,RW}
      libnvdimm: Convert to DEVICE_ATTR_ADMIN_RO()
      PM, libnvdimm: Add runtime firmware activation support
      ACPI: NFIT: Add runtime firmware activate support
      ACPI: NFIT: Fix ARS zero-sized allocation

Hao Li (1):
      dax: Fix incorrect argument passed to xas_set_err()

Ira Weiny (2):
      fs/dax: Remove unused size parameter
      drivers/dax: Expand lock scope to cover the use of addresses

Jane Chu (3):
      libnvdimm/security: fix a typo
      libnvdimm/security: the 'security' attr never show 'overwrite' state
      libnvdimm/security: ensure sysfs poll thread woke up and fetch updated attr

Vishal Verma (2):
      Merge branch 'for-5.9/dax' into libnvdimm-for-next
      Merge branch 'for-5.9/firmware-activate' into libnvdimm-for-next

 Documentation/ABI/testing/sysfs-bus-nfit           |  19 +
 Documentation/ABI/testing/sysfs-bus-nvdimm         |   2 +
 .../driver-api/nvdimm/firmware-activate.rst        |  86 +++++
 drivers/acpi/nfit/core.c                           | 157 ++++++---
 drivers/acpi/nfit/intel.c                          | 386 +++++++++++++++++++++
 drivers/acpi/nfit/intel.h                          |  61 ++++
 drivers/acpi/nfit/nfit.h                           |  38 +-
 drivers/dax/super.c                                |  13 +-
 drivers/nvdimm/bus.c                               |  16 +
 drivers/nvdimm/core.c                              | 149 ++++++++
 drivers/nvdimm/dimm_devs.c                         | 123 ++++++-
 drivers/nvdimm/namespace_devs.c                    |   2 +-
 drivers/nvdimm/nd-core.h                           |   1 +
 drivers/nvdimm/pfn_devs.c                          |   2 +-
 drivers/nvdimm/region_devs.c                       |   2 +-
 drivers/nvdimm/security.c                          |  13 +-
 fs/dax.c                                           |  15 +-
 include/linux/device.h                             |   4 +
 include/linux/libnvdimm.h                          |  52 ++-
 include/linux/suspend.h                            |   6 +
 include/linux/sysfs.h                              |   7 +
 include/uapi/linux/ndctl.h                         |   5 +
 kernel/power/hibernate.c                           |  97 ++++++
 tools/testing/nvdimm/test/nfit.c                   | 367 ++++++++++++++++----
 24 files changed, 1486 insertions(+), 137 deletions(-)
 create mode 100644 Documentation/ABI/testing/sysfs-bus-nvdimm
 create mode 100644 Documentation/driver-api/nvdimm/firmware-activate.rst

             reply	other threads:[~2020-08-11  1:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11  1:20 Verma, Vishal L [this message]
2020-08-11 20:27 ` [GIT PULL] libnvdimm for v5.9 pr-tracker-bot

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=f44b21c38313fa8e19a3e70eb285e0dd319eb421.camel@intel.com \
    --to=vishal.l.verma@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=gregkh@linuxfoundation.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).