From: Peter Maydell <peter.maydell@linaro.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] cpu: cpu_save/cpu_load is no more
Date: Sat, 30 Jan 2016 15:16:01 +0000 [thread overview]
Message-ID: <CAFEAcA8GPeR9BmQVQUpipFeBOArMO7LYbnTdTGeS39aC2=bm-Q@mail.gmail.com> (raw)
In-Reply-To: <56AC840E.5000303@msgid.tls.msk.ru>
On 30 January 2016 at 09:36, Michael Tokarev <mjt@tls.msk.ru> wrote:
> 19.01.2016 15:08, Paolo Bonzini wrote:
>> Everything has been converted to vmstate.
>
> Applied to -trivial, thanks!
Ah, I missed that Paolo had sent out this patch before me
(my version is http://patchwork.ozlabs.org/patch/572694/ but
a week later...)
thanks
-- PMM
prev parent reply other threads:[~2016-01-30 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 12:08 [Qemu-devel] [PATCH] cpu: cpu_save/cpu_load is no more Paolo Bonzini
2016-01-30 9:36 ` Michael Tokarev
2016-01-30 15:16 ` Peter Maydell [this message]
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='CAFEAcA8GPeR9BmQVQUpipFeBOArMO7LYbnTdTGeS39aC2=bm-Q@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).