From: Paolo Bonzini <pbonzini@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: lvivier@redhat.com, peter.maydell@linaro.org,
mtosatti@redhat.com, agraf@suse.de, qemu-devel@nongnu.org,
qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] vl: Move cpu_synchronize_all_states() into qemu_system_reset()
Date: Mon, 4 Apr 2016 10:33:06 +0200 [thread overview]
Message-ID: <570226C2.1070304@redhat.com> (raw)
In-Reply-To: <20160404075435.GN16485@voom.fritz.box>
On 04/04/2016 09:54, David Gibson wrote:
> > Acked-by: Paolo Bonzini <pbonzini@redhat.com>
>
> Paolo / Peter, should I send this in a pull request for my tree, or
> should it go through someone else's tree?
Go ahead and send it.
Paolo
next prev parent reply other threads:[~2016-04-04 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 4:49 [Qemu-devel] [PATCH] vl: Move cpu_synchronize_all_states() into qemu_system_reset() David Gibson
2016-04-04 7:31 ` Paolo Bonzini
2016-04-04 7:54 ` David Gibson
2016-04-04 8:33 ` Paolo Bonzini [this message]
2016-04-04 8:24 ` Laurent Vivier
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=570226C2.1070304@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=mtosatti@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).