From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>,
Simon Ruderich <simon@ruderich.org>
Cc: qemu-devel@nongnu.org,
Peter Crosthwaite <crosthwaitepeter@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
David Alan Gilbert <dgilbert@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v8 6/7] qmp: add pmemload command
Date: Wed, 28 Nov 2018 10:43:56 -0600 [thread overview]
Message-ID: <e343f966-ef6d-73d1-6bc2-f1801df1ba03@redhat.com> (raw)
In-Reply-To: <87r2f5fke5.fsf@dusky.pond.sub.org>
On 11/28/18 6:37 AM, Markus Armbruster wrote:
...
>
> @offset and @size feel a bit like overengineering to me. If this work
> was still at the design stage, I'd advise to start without them, then
> see whether there's a genuine need. At v5, I'm li
>
>
Was there intended to be more to this message?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-11-28 16:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 14:07 [Qemu-devel] [PATCH v8 0/7] qmp: add pmemload command Simon Ruderich
2018-11-15 14:07 ` [Qemu-devel] [PATCH v8 1/7] cpus: correct coding style in qmp_memsave/qmp_pmemsave Simon Ruderich
2018-11-15 14:07 ` [Qemu-devel] [PATCH v8 2/7] cpus: convert qmp_memsave/qmp_pmemsave to use qemu_open Simon Ruderich
2018-11-15 14:07 ` [Qemu-devel] [PATCH v8 3/7] cpus: use size_t in qmp_memsave/qmp_pmemsave Simon Ruderich
2018-11-15 14:07 ` [Qemu-devel] [PATCH v8 4/7] hmp: use l for size argument in memsave/pmemsave Simon Ruderich
2018-11-15 14:07 ` [Qemu-devel] [PATCH v8 5/7] hmp: use F for filename arguments " Simon Ruderich
2018-11-15 14:07 ` [Qemu-devel] [PATCH v8 6/7] qmp: add pmemload command Simon Ruderich
2018-11-28 12:37 ` Markus Armbruster
2018-11-28 16:43 ` Eric Blake [this message]
2018-11-28 18:07 ` Markus Armbruster
2018-11-15 14:07 ` [Qemu-devel] [PATCH v8 7/7] hmp: " Simon Ruderich
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=e343f966-ef6d-73d1-6bc2-f1801df1ba03@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=crosthwaitepeter@gmail.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=simon@ruderich.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).