Adding upstream version 1.0.
Signed-off-by: Daniel Baumann <daniel@debian.org>
This commit is contained in:
parent
809e3412a9
commit
336fe81026
743 changed files with 51081 additions and 0 deletions
21
doc/man/nvme_security_send.2
Normal file
21
doc/man/nvme_security_send.2
Normal file
|
@ -0,0 +1,21 @@
|
|||
.TH "nvme_security_send" 9 "nvme_security_send" "April 2022" "libnvme API manual" LINUX
|
||||
.SH NAME
|
||||
nvme_security_send \-
|
||||
.SH SYNOPSIS
|
||||
.B "int" nvme_security_send
|
||||
.BI "(struct nvme_security_send_args *args " ");"
|
||||
.SH ARGUMENTS
|
||||
.IP "args" 12
|
||||
\fIstruct nvme_security_send\fP argument structure
|
||||
.SH "DESCRIPTION"
|
||||
The Security Send command transfers security protocol data to the
|
||||
controller. The data structure transferred to the controller as part of this
|
||||
command contains security protocol specific commands to be performed by the
|
||||
controller. The data structure transferred may also contain data or
|
||||
parameters associated with the security protocol commands.
|
||||
|
||||
The security data is protocol specific and is not defined by the NVMe
|
||||
specification.
|
||||
.SH "RETURN"
|
||||
The nvme command status if a response was received (see
|
||||
\fIenum nvme_status_field\fP) or -1 with errno set otherwise.
|
Loading…
Add table
Add a link
Reference in a new issue