All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kashyap Chamarthy <kchamart@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: kwolf@redhat.com, John Snow <jsnow@redhat.com>,
	qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] qmp-commands.hx: Update the supported 'transaction' operations
Date: Sat, 25 Apr 2015 19:18:29 +0200	[thread overview]
Message-ID: <20150425171829.GA13856@tesla.redhat.com> (raw)
In-Reply-To: <553AACEF.1050405@redhat.com>

On Fri, Apr 24, 2015 at 02:51:59PM -0600, Eric Blake wrote:
> On 04/24/2015 10:20 AM, Kashyap Chamarthy wrote:
> > On Fri, Apr 24, 2015 at 11:52:00AM -0400, John Snow wrote:
> >>
> >> On 04/24/2015 04:32 AM, Kashyap Chamarthy wrote:
> > 
> > [. . .]
> > 
> >> These:
> >>
> >>>     block-dirty-bitmap-add
> >>>     block-dirty-bitmap-clear
> >>>
> >>
> >> Aren't merged yet, so it might be a little confusing.
> > 
> > Yeah, I expected someone to call that out, that's the reason I added the
> > NB at the end of the commit message which explicitly states that these
> > will be usable once your series (linked below) is merged, hoping that'd
> > clarify.
> > 
> >> We could tack this on to the end of the transaction series if you'd
> >> like, and hopefully that all goes in at once before 2.4.
> > 
> > That works too. 
> > 
> > If it's preferable, I can respin this to remove the mention of above two
> > commands and resubmit a v3. 
> 
> I would have just added a note after the '---' line that the patch
> depends on the transaction series going in first.  That is, basically
> appending this on to the end of the transaction series is the best
> approach for now, rather than trying to respin without the new
> commands.

Agreed. 

John: as you suggested, too, please "tack this on to the end of" your
transaction patch series.

Thanks.

-- 
/kashyap

  reply	other threads:[~2015-04-25 17:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-24  8:32 [Qemu-devel] [PATCH v2] qmp-commands.hx: Update the supported 'transaction' operations Kashyap Chamarthy
2015-04-24 15:52 ` John Snow
2015-04-24 16:20   ` Kashyap Chamarthy
2015-04-24 16:21     ` John Snow
2015-04-24 20:51     ` Eric Blake
2015-04-25 17:18       ` Kashyap Chamarthy [this message]
2015-04-27  9:47 ` Stefan Hajnoczi

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=20150425171829.GA13856@tesla.redhat.com \
    --to=kchamart@redhat.com \
    --cc=eblake@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lcapitulino@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.