From: Alison Schofield <alison.schofield@intel.com>
To: <nvdimm@lists.linux.dev>, <linux-cxl@vger.kernel.org>
Subject: [ANNOUNCE] ndctl v84
Date: Sat, 14 Mar 2026 18:33:34 -0700 [thread overview]
Message-ID: <abYMbjGetB44Nqbg@aschofie-mobl2.lan> (raw)
A new NDCTL release is available[1].
This release incorporates functionality up through the 7.0 kernel.
Highlights include new cxl-cli commands for media and protocol error
injection, visibility of Extended Linear Cache (ELC) in cxl-list along
with a new ELC unit test, and a unit test for address translation. It
also includes additional unit test and infrastructure improvements that
improve test coverage and overall quality.
Thanks to Ben, Dave and all the users, reviewers, and reporters!
A shortlog is appended below.
[1] https://github.com/pmem/ndctl/releases/tag/v84
Alison Schofield (9):
README.md: exclude unsupported distros from Repology badge
test/pmem-ns: fully reset nfit_test in pmem-ns unit test
test/cxl-translate.sh: add new cxl-translate.sh unit test
daxctl: replace basename() usage with new path_basename()
test/cxl-poison.sh: add test case for unaligned address translations
test/cxl-topology.sh: test switch port target enumeration
util/sysfs: save and use errno properly in read and write paths
util/sysfs: add hint for missing root privileges on sysfs access
test/cxl-poison.sh: replace sysfs usage with cxl-cli cmds
Ben Cheatham (7):
libcxl: add debugfs path to CXL context
libcxl: add CXL protocol errors
libcxl: add poison injection support
cxl: add inject-protocol-error command
cxl: add poison injection/clear commands
cxl/list: add injectable errors in output
Documentation: add docs for protocol and poison injection commands
Dave Jiang (6):
cxl: add support for extended linear cache
test/cxl-poison.sh: detect the correct elc sysfs attribute
test/cxl-poison.sh: use the cxl_test auto region
test/cxl-elc.sh: add a new test for extended linear cache support
test/cxl-poison.sh: add support for ELC in poison test
ndctl: add key cleanup after overwrite operation
reply other threads:[~2026-03-15 1:33 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=abYMbjGetB44Nqbg@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
/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