qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Kashyap Chamarthy <kchamart@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH v2] qapi/block-core.json: Remove stale description of 'blockdev-add'
Date: Wed, 5 Aug 2020 09:20:43 -0500	[thread overview]
Message-ID: <792dfd44-d514-8db8-0409-d9ac6750f914@redhat.com> (raw)
In-Reply-To: <20200805100158.1239390-1-kchamart@redhat.com>

On 8/5/20 5:01 AM, Kashyap Chamarthy wrote:
> On a 'qemu-discuss' thread[1], Kevin identifies that the current doc
> blurb for @blockdev-add is stale:
> 
>      This is actually a documentation bug. @id doesn't exist,
>      blockdev-add never creates a BlockBackend. This was different in the
>      very first versions of the patches to add blockdev-add and we
>      probably just forgot to update the documentation after removing it.
> 
> So remove the stale bits.
> 
> And the requirement for 'node-name' is already mentioned in the
> documentation of @BlockdevOptions:
> 
>      [...]
>      # @node-name: the node name of the new node (Since 2.0).
>      #             This option is required on the top level of blockdev-add.
>      #             Valid node names start with an alphabetic character and may
>      #             contain only alphanumeric characters, '-', '.' and '_'. Their
>      #             maximum length is 31 characters.
>      [...]
> 
> [1] https://lists.nongnu.org/archive/html/qemu-discuss/2020-07/msg00071.html
>      -- equivalent to "-drive if=ide,id=disk0....."
> 
> Fixes: be4b67bc7d ("blockdev: Allow creation of BDS trees without BB")
> 
> Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
> Suggested-by: Kevin Wolf <kwolf@redhat.com>
> ---

Reviewed-by: Eric Blake <eblake@redhat.com>

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org



  reply	other threads:[~2020-08-05 14:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05 10:01 [PATCH v2] qapi/block-core.json: Remove stale description of 'blockdev-add' Kashyap Chamarthy
2020-08-05 14:20 ` Eric Blake [this message]
2020-09-02 15:59 ` Markus Armbruster

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=792dfd44-d514-8db8-0409-d9ac6750f914@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kchamart@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).