nvme/libnvme
1
0
Fork 0
Code Issues Activity

Merging upstream version 1.9.

Browse source 
Signed-off-by: Daniel Baumann <daniel@debian.org>
This commit is contained in:
Daniel Baumann 2025-02-16 10:50:33 +01:00
parent 432344d511
commit ff5afdb431
Signed by: daniel
GPG key ID: FBB4F0E80A80222F
928 changed files with 6732 additions and 1442 deletions
Download patch file Download diff file Expand all files Collapse all files

24
doc/man/nvme_scan_tls_keys.2 Normal file
View file

@ -0,0 +1,24 @@
.TH "nvme_scan_tls_keys" 9 "nvme_scan_tls_keys" "May 2024" "libnvme API manual" LINUX
.SH NAME
nvme_scan_tls_keys \- Iterate over TLS keys in a keyring
.SH SYNOPSIS
.B "int" nvme_scan_tls_keys
.BI "(const char *keyring " ","
.BI "nvme_scan_tls_keys_cb_t cb " ","
.BI "void *data " ");"
.SH ARGUMENTS
.IP "keyring" 12
Keyring holding TLS keys
.IP "cb" 12
Callback function
.IP "data" 12
Pointer for data to be passed to \fIcb\fP
.SH "DESCRIPTION"
Iterates \fIkeyring\fP and call \fIcb\fP for each TLS key. When \fIkeyring\fP is NULL
the default '.nvme' keyring is used.
A TLS key must be of type 'psk' and the description must be of the
form 'NVMe<0|1><R|G>0<1|2> <identity>', otherwise it will be skipped
during iteration.
.SH "RETURN"
Number of keys for which \fIcb\fP was called, or -1 with errno set
on error.