[Nbd] [PATCH] doc: Fix some minor issues
- To: nbd-general@lists.sourceforge.net
- Subject: [Nbd] [PATCH] doc: Fix some minor issues
- From: Eric Blake <eblake@...696...>
- Date: Thu, 16 Feb 2017 17:19:36 -0600
- Message-id: <20170216231936.1474-1-eblake@...696...>
- In-reply-to: <20170216230452.31325-1-eblake@...696...>
- References: <20170216230452.31325-1-eblake@...696...>
Fix a grammar nit and typo, and resolve a conflict between two
extensions picking the same command number (BLOCK_STATUS is the
older proposal, so it keeps command 7, RESIZE gets command 8).
Signed-off-by: Eric Blake <eblake@...696...>
---
Counterpart patch for the extension-resize branch
doc/proto.md | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/doc/proto.md b/doc/proto.md
index a4deace..90a073a 100644
--- a/doc/proto.md
+++ b/doc/proto.md
@@ -287,7 +287,7 @@ order, except that:
* All write commands (that includes `NBD_CMD_WRITE`,
`NBD_CMD_WRITE_ZEROES` and `NBD_CMD_TRIM`) that the server
- completes (i.e. replies to) prior to processing to a
+ completes (i.e. replies to) prior to processing a
`NBD_CMD_FLUSH` MUST be written to non-volatile
storage prior to replying to that `NBD_CMD_FLUSH`. This
paragraph only applies if `NBD_FLAG_SEND_FLUSH` is set within
@@ -990,7 +990,12 @@ The following request types exist:
including one or more sectors beyond the size of the device. It SHOULD
return `EPERM` if it receives a write zeroes request on a read-only export.
-* `NBD_CMD_RESIZE` (7)
+* `NBD_CMD_BLOCK_STATUS` (7)
+
+ Defined by the experimental `BLOCK_STATUS`
+ [extension](https://github.com/NetworkBlockDevice/nbd/blob/extension-blockstatus/doc/proto.md).
+
+* `NBD_CMD_RESIZE` (8)
A resize request. The server should make the necessary changes by
either allocating more space or releasing space that is no longer
--
2.9.3
Reply to: