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 v78
Date: Thu, 3 Aug 2023 22:28:56 +0000 [thread overview]
Message-ID: <8a83f1832c95e327a4695b607729102216a3e2f0.camel@intel.com> (raw)
A new ndctl release is available[1].
This release incorporates functionality up to the 6.5 kernel.
Highlights include fixes to cxl-monitor and ndctl-monitor, a new
cxl-update-firmware command, various documentation fixes, and a new unit
test for cxl events.
A shortlog is appended below.
[1]: https://github.com/pmem/ndctl/releases/tag/v78
---
Davidlohr Bueso (1):
ndctl/security: fix Theory of Operation typos
Dmitry V. Levin (1):
daxctl: fix warning reported by udevadm verify
Ira Weiny (1):
ndctl/cxl/test: Add CXL event test
Li Zhijian (9):
rpmbuild.sh: Abort script when an error occurs
meson.build: add libtracefs version >=1.2.0 dependency
cxl/monitor: Enable default_log and refactor sanity checks
cxl/monitor: replace monitor.log_file with monitor.ctx.log_file
ndctl: use strcmp for reserved word in monitor commands
Documentation/cxl/cxl-monitor.txt: Remove mention of syslog output
CONTRIBUTING.md: Add note about the CXL mailing list
README.md: document setup steps for CXL unit tests
cxl/region: Fix memdevs leak in parse_create_options()
Minwoo Im (3):
cxl/list: Fix typo in cxl-list documentation
cxl: region: remove redundant func name from error
cxl: fix changed function name in a comment
Vishal Verma (6):
cxl/memdev.c: allow filtering memdevs by bus
cxl/list: print firmware info in memdev listings
cxl/fw_loader: add APIs to get current state of the FW loader mechanism
cxl: add an update-firmware command
test/cxl-update-firmware: add a unit test for firmware update
cxl/memdev: initialize 'rc' in action_update_fw()
Yi Zhang (2):
typo fix: ovewrite -> overwrite
README.md: add three additional config to config item list
reply other threads:[~2023-08-03 22:29 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=8a83f1832c95e327a4695b607729102216a3e2f0.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