qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: "Bryan D. Payne" <bdpayne@acm.org>, qemu-devel@nongnu.org
Cc: lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] qmp: extend QMP to provide read/write access to physical memory
Date: Mon, 01 Dec 2014 15:12:09 -0700	[thread overview]
Message-ID: <547CE7B9.5090503@redhat.com> (raw)
In-Reply-To: <1417033667-10364-1-git-send-email-bdpayne@acm.org>

[-- Attachment #1: Type: text/plain, Size: 720 bytes --]

On 11/26/2014 01:27 PM, Bryan D. Payne wrote:
> Thanks for the feedback Eric, I've updated the patch.
> 
> v2 changes:
> - added QMP command contract to qapi-schema.json
> - corrected some comments
> - rewired QMP command to use schema code

When sending a v2, it's best to send it as a new top-level thread,
instead of buried in-reply-to an existing thread.  Also, for a single
patch, a cover letter is not strictly necessary (the information you
gave here can instead be given after the --- separator of the
one-and-only patch email).  Cover letters are mandatory only for
multi-patch series.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 539 bytes --]

  parent reply	other threads:[~2014-12-01 22:12 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26  8:41 [Qemu-devel] [PATCH 0/1] qmp: extend QMP to provide read/write access to physical memory Bryan D. Payne
2014-11-26  8:41 ` [Qemu-devel] [PATCH 1/1] " Bryan D. Payne
2014-11-26 15:16   ` Eric Blake
2014-11-26 20:27 ` [Qemu-devel] [PATCH v2] " Bryan D. Payne
2014-11-26 20:27   ` [Qemu-devel] [PATCH] " Bryan D. Payne
2014-11-27  2:04     ` Fam Zheng
2014-12-04  3:37       ` Bryan D. Payne
2014-12-04  4:57         ` Fam Zheng
2014-12-04  6:28           ` Bryan D. Payne
2014-12-04  7:38             ` Fam Zheng
2014-12-04 16:43               ` Bryan D. Payne
2014-12-05  1:20                 ` Fam Zheng
2014-12-04  9:08         ` Markus Armbruster
2014-12-04 16:49           ` Bryan D. Payne
2014-12-05  8:44             ` Markus Armbruster
2014-12-05 21:25               ` Bryan D. Payne
2014-12-08 15:06                 ` Markus Armbruster
2014-12-09 15:12                   ` Bryan D. Payne
2014-12-11  3:33                     ` Bryan D. Payne
2014-12-11  5:45                       ` Fam Zheng
2014-12-11  6:07                         ` Bryan D. Payne
2014-12-12  2:28                         ` Bryan D. Payne
2014-12-12  3:29                           ` Fam Zheng
2014-12-01 22:10     ` Eric Blake
2014-12-03 23:07       ` Bryan D. Payne
2014-12-04 15:08         ` Eric Blake
2014-12-04 16:50           ` Bryan D. Payne
2014-12-04 18:40           ` Bryan D. Payne
2014-12-04 22:43             ` Eric Blake
2014-12-01 22:12   ` Eric Blake [this message]
2014-12-02  4:36     ` [Qemu-devel] [PATCH v2] " Bryan D. Payne
2014-12-02  5:26       ` Fam Zheng

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=547CE7B9.5090503@redhat.com \
    --to=eblake@redhat.com \
    --cc=bdpayne@acm.org \
    --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 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).