From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>
Subject: [ANNOUNCE] ndctl v69
Date: Thu, 23 Jul 2020 05:57:56 +0000 [thread overview]
Message-ID: <4205dc57a8ebfef2698fa09c8029f32efed6c3dd.camel@intel.com> (raw)
A new ndctl release is available[1].
Highlights include support for 'PAPR' NVDIMMs, a build fix for
zero-length array warnings in GCC10, a new option for ndctl-monitor
allowing for a timeout for epoll, and misc unit test and documentation
fixes.
A shortlog is appended below.
[1]: https://github.com/pmem/ndctl/releases/tag/v69
Dan Williams (1):
ndctl/build: Fix zero-length array warnings
Michal Suchanek (1):
Documentation: use includes in more ndctl command pages.
Santosh Sivaraj (2):
Skip region filtering if numa_node attribute is not present
infoblock: Set the default alignment to the platform alignment
Steve Scargall (1):
ndctl/doc: Fix a typo in Documentation/daxctl/movable-options.txt
Vaibhav Jain (8):
libndctl: Refactor out add_dimm() to handle NFIT specific init
libncdtl: Add initial support for NVDIMM_FAMILY_PAPR nvdimm family
libndctl,papr_scm: Add definitions for PAPR nvdimm specific methods
papr: Add scaffolding to issue and handle PDSM requests
libndctl,papr_scm: Implement support for PAPR_PDSM_HEALTH
monitor: Add epoll timeout for forcing a full dimm health check
libndctl/papr_scm: Add support for reporting "life_used_percentage" metric
papr: Check for command type in papr_xlat_firmware_status()
Vishal Verma (5):
ndctl/test: Fix region selection in align.sh
ndctl/test: fix align.sh to not expect initialized labels
ndctl/README: Add CONFIG_ENCRYPTED_KEYS to the config items list
ndctl/namespace: fix a resource leak in file_write_infoblock()
ndctl/lib: fix new symbol location in the symbol script
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
reply other threads:[~2020-07-23 5:58 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=4205dc57a8ebfef2698fa09c8029f32efed6c3dd.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=dan.j.williams@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