qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, stefanha@redhat.com, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/1] iscsi: add missing colons to the qapi docs
Date: Mon, 27 Feb 2017 23:33:18 -0500	[thread overview]
Message-ID: <20170228043318.GP25637@localhost.localdomain> (raw)
In-Reply-To: <cb5d66c64225db82c115f54becee38a659cd578e.1488256020.git.jcody@redhat.com>

On Mon, Feb 27, 2017 at 11:29:07PM -0500, Jeff Cody wrote:
> The missing colons make the iscsi part of the documentation not render
> quite as nicely, so add those in.
> 
> Signed-off-by: Jeff Cody <jcody@redhat.com>
> ---
>  qapi/block-core.json | 18 +++++++++---------
>  1 file changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/qapi/block-core.json b/qapi/block-core.json
> index 5f82d35..cf24c04 100644
> --- a/qapi/block-core.json
> +++ b/qapi/block-core.json
> @@ -2625,29 +2625,29 @@
>  ##
>  # @BlockdevOptionsIscsi:
>  #
> -# @transport        The iscsi transport type
> +# @transport:       The iscsi transport type
>  #
> -# @portal           The address of the iscsi portal
> +# @portal:          The address of the iscsi portal
>  #
> -# @target           The target iqn name
> +# @target:          The target iqn name
>  #
> -# @lun              #optional LUN to connect to. Defaults to 0.
> +# @lun:             #optional LUN to connect to. Defaults to 0.
>  #
> -# @user             #optional User name to log in with. If omitted, no CHAP
> +# @user:            #optional User name to log in with. If omitted, no CHAP
>  #                   authentication is performed.
>  #
> -# @password-secret  #optional The ID of a QCryptoSecret object providing
> +# @password-secret: #optional The ID of a QCryptoSecret object providing
>  #                   the password for the login. This option is required if
>  #                   @user is specified.
>  #
> -# @initiator-name   #optional The iqn name we want to identify to the target
> +# @initiator-name:  #optional The iqn name we want to identify to the target
>  #                   as. If this option is not specified, an initiator name is
>  #                   generated automatically.
>  #
> -# @header-digest    #optional The desired header digest. Defaults to
> +# @header-digest:   #optional The desired header digest. Defaults to
>  #                   none-crc32c.
>  #
> -# @timeout          #optional Timeout in seconds after which a request will
> +# @timeout:         #optional Timeout in seconds after which a request will
>  #                   timeout. 0 means no timeout and is the default.
>  #
>  # Driver specific block device options for iscsi
> -- 
> 2.9.3
> 

Thanks,

Applied to my block branch:

git://github.com/codyprime/qemu-kvm-jtc.git block

-Jeff

      reply	other threads:[~2017-02-28  4:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28  4:29 [Qemu-devel] [PATCH 1/1] iscsi: add missing colons to the qapi docs Jeff Cody
2017-02-28  4:33 ` Jeff Cody [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170228043318.GP25637@localhost.localdomain \
    --to=jcody@redhat.com \
    --cc=armbru@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).