Merging upstream version 2.0.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 48 insertions, 0 deletions

diff --git a/Documentation/nvme-wdc-get-unsupported-reqs-log.txt b/Documentation/nvme-wdc-get-unsupported-reqs-log.txt
new file mode 100644
index 0000000..f028665
--- /dev/null
+++ b/Documentation/nvme-wdc-get-unsupported-reqs-log.txt
@@ -0,0 +1,48 @@
+nvme-wdc-get-unsupported-reqs-log(1)
+====================================
+
+NAME
+----
+nvme-wdc-get-unsupported-reqs-log - Send NVMe WDC get-unsupported-reqs-log 
+									plugin command, return parsed log output
+
+SYNOPSIS
+--------
+[verse]
+'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.