From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43880) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d9GGg-0005lG-Pd for qemu-devel@nongnu.org; Fri, 12 May 2017 15:30:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d9GGb-0000ZV-O1 for qemu-devel@nongnu.org; Fri, 12 May 2017 15:30:26 -0400 From: Eric Blake Date: Fri, 12 May 2017 14:30:15 -0500 Message-Id: <20170512193015.22155-1-eblake@redhat.com> Subject: [Qemu-devel] [PATCH] block: Correct documentation for BLOCK_WRITE_THRESHOLD List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: qemu-trivial@nongnu.org, Markus Armbruster Use the correct command name. Signed-off-by: Eric Blake --- qapi/block-core.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/qapi/block-core.json b/qapi/block-core.json index 614181b..206e33b 100644 --- a/qapi/block-core.json +++ b/qapi/block-core.json @@ -3582,7 +3582,7 @@ # means the device should be extended to avoid pausing for # disk exhaustion. # The event is one shot. Once triggered, it needs to be -# re-registered with another block-set-threshold command. +# re-registered with another block-set-write-threshold command. # # @node-name: graph node name on which the threshold was exceeded. # -- 2.9.3