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>
Subject: [ANNOUNCE] ndctl v77
Date: Tue, 2 May 2023 20:32:18 +0000 [thread overview]
Message-ID: <5de1dbdeb8484c91ca6a159d48b9f01e7afb2407.camel@intel.com> (raw)
A new ndctl release is available[1].
This release incorporates functionality up to the 6.3 kernel.
Highlights include some build fixes around cx-monitor and event tracing,
the ability to create ram type regions, some fixes to create-region to
allow a user-supplied UUID, cxl-list fixes for RCD devices, and region
listings, cxl-list filtering improvements, and some unit test fixes.
A shortlog is appended below.
[1]: https://github.com/pmem/ndctl/releases/tag/v77
Dan Williams (8):
cxl/monitor: Make libtracefs dependency optional
cxl/list: Include regions in the verbose listing
cxl/list: Enumerate device-dax properties for regions
cxl/list: Fix filtering RCDs
cxl/list: Filter root decoders by region
test: Support test modules located in 'updates' instead of 'extra'
test: Fix dangling pointer warning
cxl/list: Add parent_dport attribute to port listings
Vishal Verma (8):
cxl/monitor: fix include paths for tracefs and traceevent
cxl/event-trace: use the wrapped util_json_new_u64()
cxl/region: skip region_actions for region creation
cxl: add a type attribute to region listings
cxl: add core plumbing for creation of ram regions
cxl/region: accept user-supplied UUIDs for pmem regions
cxl/region: determine region type based on root decoder capability
ndctl/namespace.c: fix unchecked return value from uuid_parse()
Xiao Yang (1):
test/security.sh: Replace cxl with $CXL
reply other threads:[~2023-05-02 20:32 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=5de1dbdeb8484c91ca6a159d48b9f01e7afb2407.camel@intel.com \
--to=vishal.l.verma@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