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 v76
Date: Wed, 22 Feb 2023 22:46:40 +0000 [thread overview]
Message-ID: <04fb4f86929c557033ab3e55a0742b0dfaa87dee.camel@intel.com> (raw)
A new ndctl release is available[1].
Highlights include the new cxl-monitor command that uses CXL trace
events, fix for a long-standing off-by-one in memblock enumeration in
libdaxctl, another daxctl fix to be tolerant of new sysfs attributes
starting with 'memory_', that are not regular memblocks, and a few
other misc cleanups and fixes.
A shortlog is appended below.
[1]: https://github.com/pmem/ndctl/releases/tag/v76
Adam Manzanares (1):
daxctl: Skip over memory failure node status
Alexander Motin (4):
libndctl/msft: Remove NDN_MSFT_SMART_*_VALID defines.
libndctl/msft: Replace nonsense NDN_MSFT_CMD_SMART command
libndctl/msft: Add custom cmd_is_supported() method
libndctl/msft: Improve smart state reporting
Dan Williams (1):
daxctl: Fix memblock enumeration off-by-one
Dave Jiang (7):
cxl: add a helper to parse trace events into a json object
cxl: add a helper to go through all current events and parse them
cxl: add a common function to enable/disable event tracing
ndctl/monitor: move common logging functions to util/log.c
cxl/monitor: add a new monitor command for CXL trace events
cxl: add a systemd service for cxl-monitor
cxl/monitor: add man page documentation for the monitor command
Ira Weiny (1):
ndctl/cxl: Remove unnecessary null check
Vishal Verma (6):
test/cxl-xor-region.sh: skip instead of fail for missing cxl_test
meson.build: fix version for v75
cxl/event_trace: fix a resource leak in cxl_event_to_json()
cxl/monitor: retain error code in monitor_event()
test/cxl-security.sh: avoid intermittent failures due to async probe
ndctl.spec.in: Add build dependencies for libtraceevent and libtracefs
reply other threads:[~2023-02-22 22:46 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=04fb4f86929c557033ab3e55a0742b0dfaa87dee.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