nvme/libnvme
1
0
Fork 0
Code Issues Activity

Merging upstream version 1.1~rc0.

Browse source 
Signed-off-by: Daniel Baumann <daniel@debian.org>
This commit is contained in:
Daniel Baumann 2025-02-16 10:03:28 +01:00
parent 537ee18b08
commit 73281abe5f
Signed by: daniel
GPG key ID: FBB4F0E80A80222F
764 changed files with 32602 additions and 5874 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -0,0 +1,24 @@
.TH "nvme_mi_admin_security_recv" 9 "nvme_mi_admin_security_recv" "July 2022" "libnvme API manual" LINUX
.SH NAME
nvme_mi_admin_security_recv \- Perform a Security Receive command on a controller.
.SH SYNOPSIS
.B "int" nvme_mi_admin_security_recv
.BI "(nvme_mi_ctrl_t ctrl " ","
.BI "struct nvme_security_receive_args *args " ");"
.SH ARGUMENTS
.IP "ctrl" 12
Controller to send command to
.IP "args" 12
Security Receive command arguments
.SH "DESCRIPTION"
Performs a Security Receive Admin command as specified by \fIargs\fP. Response
data is stored in \fIargs->data\fP, which should be a buffer of \fIargs->data_len\fP
bytes. Resulting data length is stored in \fIargs->data_len\fP on successful
command completion.
Security Receive data length should not be greater than 4096 bytes to
comply with specification limits.
See: \fIstruct nvme_get_log_args\fP
.SH "RETURN"
0 on success, non-zero on failure