Opened 14 months ago
Closed 14 months ago
#19033 closed enhancement (fixed)
libnvme-1.7.1
Reported by: | Douglas R. Reno | Owned by: | Bruce Dubbs |
---|---|---|---|
Priority: | normal | Milestone: | 12.1 |
Component: | BOOK | Version: | git |
Severity: | normal | Keywords: | |
Cc: |
Description
New minor version
Change History (5)
comment:2 by , 14 months ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:3 by , 14 months ago
Now version 1.7.1
When I run the tests I get:
[0/1] Running all tests. 1/17 mi OK 0.03s 2/17 uuid OK 0.03s 3/17 tree OK 0.02s 4/17 Test util.c OK 0.02s 5/17 features OK 0.02s 6/17 identify OK 0.02s 7/17 NBFT-auto-ipv6 OK 0.02s 8/17 NBFT-dhcp-ipv6 OK 0.02s 9/17 NBFT-rhpoc OK 0.02s 10/17 NBFT-static-ipv4 OK 0.02s 11/17 NBFT-static-ipv4-discovery OK 0.01s 12/17 NBFT-static-ipv6 OK 0.01s 13/17 discovery OK 0.03s 14/17 NBFT-bad-oldspec EXPECTEDFAIL 0.01s exit status 2 15/17 NBFT-random-noise EXPECTEDFAIL 0.01s exit status 2 16/17 mi-mctp OK 0.03s 17/17 kdoc OK 0.25s
comment:4 by , 14 months ago
Summary: | libnvme-1.7 → libnvme-1.7.1 |
---|
Changes in version 1.7:
The highlights of this release are
- allocated payloads aligned
- refactoring and improvements of RAE handling in get log pages
- auto cleanup of resources
- build instruction update and improving build situation for older distros
- support for TP8018
- use sysfs only for topology scan
The last point addresses a long standing problem. Whenever 'nvme list' is used it could add error log entries for certain devices. With the corresponding kernel changes this will not happen anymore. It also unlocks some possible new features. Note this depends on the upcoming 6.8 kernel.
comment:5 by , 14 months ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Fixed at commits
073a9623ee Update to aspell-0.60.8.1. 868d29d21c Update to libnvme-1.7.1. 0c6208e8b1 Update to LibRaw-0.21.2.
Note:
See TracTickets
for help on using tickets.
There are some test failures: https://github.com/linux-nvme/libnvme/issues/762
(The report mentions two failures, but I've only seen one of them on my BLFS system.)
It seems a real issue and the fix is merged as a part of https://github.com/linux-nvme/libnvme/pull/763.
sed 's/free(ns)/return ret/' -i src/nvme/tree.c