From 589986012c4b3ab68e299a2eadca18f90080113b Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Thu, 14 Jul 2022 20:28:04 +0200 Subject: Merging upstream version 2.0. Signed-off-by: Daniel Baumann --- .../nvme-wdc-get-unsupported-reqs-log.html | 823 +++++++++++++++++++++ 1 file changed, 823 insertions(+) create mode 100644 Documentation/nvme-wdc-get-unsupported-reqs-log.html (limited to 'Documentation/nvme-wdc-get-unsupported-reqs-log.html') diff --git a/Documentation/nvme-wdc-get-unsupported-reqs-log.html b/Documentation/nvme-wdc-get-unsupported-reqs-log.html new file mode 100644 index 0000000..e1ae5d7 --- /dev/null +++ b/Documentation/nvme-wdc-get-unsupported-reqs-log.html @@ -0,0 +1,823 @@ + + + + + + +nvme-wdc-get-unsupported-reqs-log(1) + + + + + +
+
+

SYNOPSIS

+
+
+
nvme wdc get-unsupported-reqs-log <device> [--output-format=<normal|json>
+-o <normal|json>]
+
+
+
+
+
+

DESCRIPTION

+
+

For the NVMe device given, send a WDC plugin get-unsupported-reqs-log command +and output the unsupported requirements log data. The --output-format option +will format the output as specified.

+

The <device> parameter is mandatory and may be either the NVMe character +device (ex: /dev/nvme0).

+

This will only work on WDC devices supporting this log page. +Results for any other device are undefined.

+

On success it returns the parsed unsupported requirements log page data, error +code otherwise.

+
+
+
+

OPTIONS

+
+
+
+-o <format> +
+
+--output-format=<format> +
+
+

+ Set the reporting format to normal, or + json. Only one output format can be used at a time. + Default is normal. +

+
+
+
+
+
+

EXAMPLES

+
+
    +
  • +

    +Has the program issue WDC get-unsupported-reqs-log plugin command : +

    +
    +
    +
    # nvme wdc get-unsupported-reqs-log /dev/nvme0
    +
    +
    • +
+
+
+
+

NVME

+
+

Part of the nvme-user suite.

+
+
+
+
+ + + -- cgit v1.2.3