Linux-NVDIMM Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: [ANNOUNCE] ndctl v65
Date: Sat, 11 May 2019 00:13:33 +0000	[thread overview]
Message-ID: <0a3d425cd6c4e19c5f877dfbee2d55556744f3c0.camel@intel.com> (raw)

This release incorporates functionality up to the 5.1 kernel, and adds a
number of bug fixes and improvements.

Highlights include a new command to clear errors on a given namespace, a
new travis YAML configuration to enable travis builds for Ubuntu, an
example QEMU script in contrib/ for HMAT emulation, an optional poll
interval for wait-scrub, several fixes related to the security commands,
support for the HYPER-V family of DSM commands, and several fixes to
tests, documentation, and related to building.


Shortlog for this release:

Dan Williams (2):
      ndctl/bus: Add poll interval to wait-scrub
      ndctl/list: Introduce region capability objects

Dave Jiang (7):
      ndctl: preserve keys after an overwrite command
      ndctl: allow a "zero-key" for secure erase
      ndctl: add a warning about overwrite taking a long time
      ndctl: fix a typo in the ndctl-sanitize-dimm man page
      ndctl: fix load-keys for non-TPM master-keys
      ndctl: fix key blob loading for non-TPM keys
      ndctl: add a load-keys test in the security unit test

Dexuan Cui (5):
      libndctl: Implement the "smart_get_health" dimm-op for Hyper-V
      libndctl: Implement the smart_get_shutdown_count dimm-op for
Hyper-V
      ndctl, monitor: Don't require the support of
ND_CMD_SMART_THRESHOLD
      libndctl: Add a new dimm-op cmd_is_supported()
      libndctl: Implement the "cmd_is_supported" dimm-op for Hyper-V

Ira Weiny (1):
      ndctl: generalize make-git-snapshot.sh

QI Fuli (1):
      monitor: remove the requirement of a default config

Robert Elliott (3):
      autoconf: print more possible package names for <keyutils.h>
      autoconf: Check for MAP_SHARED_VALIDATE and kernel/glibc conflicts
      ndctl, test: Make tests using MAP_SYNC only include <sys/mman.h>

Steve Scargall (2):
      ndctl/Documentation: Fix typo in security man pages
      ndctl/Documentation: change disable-passphrase to remove-
passphrase

Vishal Verma (11):
      ndctl, test: fix incorrect 'ndctl' usage in security.sh
      ndctl: update README for depmod overrides, ship a sample config
      ndctl/test: add dax_pmem* modules to the test-core
      ndctl: enable 'travis-ci'
      contrib: add an example qemu setup script for HMAT emulation
      ndctl: add a 'clear-errors' command
      ndctl/namespace.c: fix a resource leak in bus_send_clear()
      ndctl/namespace.c: fix an unchecked return value
      libndctl: fix an unhandled return in
ndctl_bus_poll_scrub_completion()
      ndctl/namespace.c: fix a potential integer overflow
      ndctl: release v65

Yi Zhang (1):
      ndctl/region: fix error propagation in region_action()

Łukasz Plewa (1):
      ndctl: fix a memory leak in libndctl
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

                 reply	other threads:[~2019-05-11  0:13 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=0a3d425cd6c4e19c5f877dfbee2d55556744f3c0.camel@intel.com \
    --to=vishal.l.verma@intel.com \
    --cc=linux-nvdimm@lists.01.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