qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Kashyap Chamarthy <kchamart@redhat.com>
Cc: John Snow <jsnow@redhat.com>,
	mreitz@redhat.com, qemu-devel@nongnu.org, qemu-block@nongnu.org,
	armbru@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v2] qapi: block-core: Clarify events emitted by 'block-job-cancel'
Date: Fri, 17 Nov 2017 11:49:05 +0100	[thread overview]
Message-ID: <20171117104905.GA4795@localhost.localdomain> (raw)
In-Reply-To: <20171116091405.pleud7qrqzu5nzhb@eukaryote>

Am 16.11.2017 um 10:14 hat Kashyap Chamarthy geschrieben:
> On Wed, Nov 15, 2017 at 04:56:13PM -0500, John Snow wrote:
> > 
> > 
> > On 11/15/2017 04:54 PM, Kashyap Chamarthy wrote:
> > > On Wed, Nov 15, 2017 at 02:15:57PM -0500, John Snow wrote:
> 
> [...]
> 
> > >> is it covered sufficiently in live-block-operations.rst ?
> > > 
> > > I looked in there[2] too.  Short answer: no.  Long: In the "Live disk
> > > synchronization — drive-mirror and blockdev-mirror" section, I simply
> > > seemed to declare: 
> > > 
> > >     "Issuing the command ``block-job-cancel`` after it emits the event
> > >     ``BLOCK_JOB_CANCELLED``"
> > > 
> > > As if that's the *only* event it emits, which is clearly not the case.
> > > So while at it, wonder if should I also update it
> > > ('live-block-operations.rst') too.
> > > 
> > 
> > It's an interesting gotcha that I wasn't really acutely aware of myself,
> > so having it in the doc format for API programmers who aren't
> > necessarily digging through our source sounds like a pleasant courtesy.
> 
> Indeed, will do.  (Just for my own clarity, did you imply: don't update
> it in block-core.json?  FWIW, my first instinct is to check the QAPI
> documentation for such things, that's why I wrote there first :-))

Will that be a separate patch or do you intend to send a v3?

Kevin

  parent reply	other threads:[~2017-11-17 10:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-15  9:09 [Qemu-devel] [PATCH v2] qapi: block-core: Clarify events emitted by 'block-job-cancel' Kashyap Chamarthy
2017-11-15 19:15 ` [Qemu-devel] [Qemu-block] " John Snow
2017-11-15 21:54   ` Kashyap Chamarthy
2017-11-15 21:56     ` John Snow
2017-11-16  9:14       ` Kashyap Chamarthy
2017-11-16 21:39         ` John Snow
2017-11-17 10:49         ` Kevin Wolf [this message]
2017-11-17 11:18           ` Kashyap Chamarthy

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=20171117104905.GA4795@localhost.localdomain \
    --to=kwolf@redhat.com \
    --cc=armbru@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kchamart@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).