From: Kashyap Chamarthy <kchamart@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH for-5.1?] qapi/block-core.json: Remove stale description of 'blockdev-add'
Date: Wed, 29 Jul 2020 11:22:30 +0200 [thread overview]
Message-ID: <20200729092230.4strlnuas34o54vg@paraplu> (raw)
In-Reply-To: <f285cbb4-5b40-eb38-785c-0f6ff8631321@redhat.com>
On Tue, Jul 28, 2020 at 09:50:39AM -0500, Eric Blake wrote:
> On 7/28/20 9:32 AM, Kashyap Chamarthy wrote:
[...]
> > [1] https://lists.nongnu.org/archive/html/qemu-discuss/2020-07/msg00071.html
> > -- equivalent to "-drive if=ide,id=disk0....."
> >
> > Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
> > Identified-by: Kevin Wolf <kwolf@redhat.com>
>
> This would be our first use of this unusual tag name; more typical is
> Suggested-by or Reported-by.
Yes, I agree, using predictable tags is better; so 'Suggested-by' is
good.
(We perhaps don't have as many 'unusual tags' as the kernel does :-) —
https://lwn.net/Articles/503829/)
> Is it worth a 'Fixes: be4b67bc7d' line?
Sure, including the provenance is always useful for later `git`
sleuthing.
[...]
> > -# Creates a new block device. If the @id option is given at the top level, a
> > -# BlockBackend will be created; otherwise, @node-name is mandatory at the top
> > -# level and no BlockBackend will be created.
> > +# Creates a new block device.
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
Thanks; shall I spin a v2? (I agree with both your suggestions above.)
> As a doc fix, it is safe for 5.1, but given the timing of -rc2 today, it's
> also okay if it slips into 5.2.
Yeah, 5.1 or 5.2, both are fine by me.
[...]
--
/kashyap
prev parent reply other threads:[~2020-07-29 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 14:32 [PATCH] qapi/block-core.json: Remove stale description of 'blockdev-add' Kashyap Chamarthy
2020-07-28 14:50 ` [PATCH for-5.1?] " Eric Blake
2020-07-29 9:22 ` Kashyap Chamarthy [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=20200729092230.4strlnuas34o54vg@paraplu \
--to=kchamart@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@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).