From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"nvdimm@lists.linux.dev" <nvdimm@lists.linux.dev>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
"Schofield, Alison" <alison.schofield@intel.com>
Subject: [ANNOUNCE] ndctl v79
Date: Thu, 2 May 2024 21:50:12 +0000 [thread overview]
Message-ID: <72bdf880b2cafd42163638d9e7e1d848c1d2d3a9.camel@intel.com> (raw)
A new ndctl release is available[1].
Highlights include test and build fixes, a new cxl-wait-sanitize
command, support for QOS Class in cxl-create-region, and a new
cxl-set-alert-config command.
A shortlog is appended below.
[1]: https://github.com/pmem/ndctl/releases/tag/v79
Alison Schofield (8):
cxl/test: replace a bad root decoder usage in cxl-xor-region.sh
cxl/test: validate the auto region in cxl-topology.sh
cxl/test: replace spaces with tabs in cxl-xor-region.sh
cxl/test: add double quotes in cxl-xor-region.sh
cxl/test: add 3-way HB interleave testcase to cxl-xor-region.sh
cxl/event_trace: parse arrays separately from strings
cxl/documentation: tidy up cxl-wait-sanitize man page format
cxl/test: use max_available_extent in cxl-destroy-region
Dan Williams (3):
cxl/memdev: Add a wait-sanitize command
cxl/test: Validate sanitize notifications
Build: Fix deprecated str.format() usage
Dave Jiang (10):
cxl/region: Add -f option for disable-region
cxl/Documentation: Clarify that no-op is a success for xable commands
cxl/region: Move cxl destroy_region() to new disable_region() helper
cxl: Save the number of decoders committed to a port
cxl: Add check for regions before disabling memdev
cxl/lib: Add API to retrieve QoS class for root decoders
cxl/lib: Add APIs to retrieve QoS class for memory devices
cxl: Add QoS class checks for region creation
cxl: Add a test for qos_class in CXL test suite
ndctl: cxl: Remove dependency for attributes derived from IDENTIFY command
Ira Weiny (4):
test/cxl-update-firmware: Fix checksum sysfs query
test/cxl-event: Skip cxl event testing if cxl-test is not available
cxl/region: Fix memory device teardown in disable-region
ndctl/test: Add destroy region test
Jeff Moyer (1):
test/daxctl-devices.sh: increase the namespace size to 4GiB
Jehoon Park (2):
libcxl: add support for Set Alert Configuration mailbox command
cxl: add 'set-alert-config' command to cxl tool
Jim Harris (1):
libcxl: don't calculate max_available_extent when start == ULLONG_MAX
Justin Ernst (1):
util/json: Use json_object_get_uint64() with uint64 support
Li Zhijian (3):
test/security.sh: test keyctl before excuting
test/cxl-region-sysfs.sh: use '[[ ]]' command to evaluate operands as arithmetic expressions
test/cxl-region-sysfs: fix a missing space syntax error
Osama Albahrani (1):
README: Fix a URL renaming 'master' to 'main'
Vishal Verma (4):
ndctl.spec.in: Use SPDX identifiers in License fields
test/daxctl-create.sh: remove region and dax device assumptions
daxctl/device.c: Handle special case of destroying daxX.0
daxctl/device.c: Fix error propagation in do_xaction_device()
Xiao Yang (2):
libdaxctl: Add accurate check for daxctl_memory_op(MEM_GET_ZONE)
daxctl: Remove unused memory_zone and mem_zone
reply other threads:[~2024-05-02 21:50 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=72bdf880b2cafd42163638d9e7e1d848c1d2d3a9.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).