From patchwork Fri Nov 24 08:53:49 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Fam Zheng X-Patchwork-Id: 840986 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=nongnu.org (client-ip=2001:4830:134:3::11; helo=lists.gnu.org; envelope-from=qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org; receiver=) Received: from lists.gnu.org (lists.gnu.org [IPv6:2001:4830:134:3::11]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPS id 3yjqkc68Fmz9sQl for ; Fri, 24 Nov 2017 19:54:31 +1100 (AEDT) Received: from localhost ([::1]:48044 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eI9kh-0005cG-6j for incoming@patchwork.ozlabs.org; Fri, 24 Nov 2017 03:54:27 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59490) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eI9kH-0005bc-CK for qemu-devel@nongnu.org; Fri, 24 Nov 2017 03:54:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eI9kE-0001ZQ-SO for qemu-devel@nongnu.org; Fri, 24 Nov 2017 03:54:01 -0500 Received: from mx1.redhat.com ([209.132.183.28]:37266) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eI9kE-0001Yg-Nj for qemu-devel@nongnu.org; Fri, 24 Nov 2017 03:53:58 -0500 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 760A8C04AC41; Fri, 24 Nov 2017 08:53:57 +0000 (UTC) Received: from lemon.redhat.com (ovpn-12-45.pek2.redhat.com [10.72.12.45]) by smtp.corp.redhat.com (Postfix) with ESMTP id D1EB760F89; Fri, 24 Nov 2017 08:53:52 +0000 (UTC) From: Fam Zheng To: qemu-devel@nongnu.org Date: Fri, 24 Nov 2017 16:53:49 +0800 Message-Id: <20171124085351.26386-1-famz@redhat.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Fri, 24 Nov 2017 08:53:57 +0000 (UTC) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 209.132.183.28 Subject: [Qemu-devel] [PATCH v2 0/2] docs: Add documentation for image locking X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: kwolf@redhat.com, mreitz@redhat.com, famz@redhat.com, Philipp Hahn Errors-To: qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org Sender: "Qemu-devel" v2: Grammar and spelling fixes pointed out by Kevin and Philipp. Image locking feature was added in 2.10 but the documentation has been missing. Users sometimes get confused and wonder how to configure it for their specific needs. We should address common use cases in the man page and explain related options. Fam Zheng (2): docs: Add image locking subsection qemu-options: Mention locking option of file driver docs/qemu-block-drivers.texi | 36 ++++++++++++++++++++++++++++++++++++ qemu-doc.texi | 1 + qemu-options.hx | 4 ++++ 3 files changed, 41 insertions(+)