From: Peter Maydell <peter.maydell@linaro.org>
To: Igor Mitsyanko <i.mitsyanko@gmail.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org, paul@codesourcery.com
Subject: Re: [Qemu-devel] [PATCH V2 0/2] Fix memory migration for exynos 4210 SoC
Date: Mon, 3 Jun 2013 16:05:14 +0100 [thread overview]
Message-ID: <CAFEAcA8CWf7x_34C_f_hjv4TAS+6tsf_uAyUcyfGo+rzb2+eCA@mail.gmail.com> (raw)
In-Reply-To: <1368199981-45292-1-git-send-email-i.mitsyanko@gmail.com>
On 10 May 2013 16:32, Igor Mitsyanko <i.mitsyanko@gmail.com> wrote:
> Fix issues in exynos4210 code which were blocking proper memory
> migration.
Thanks, applied to arm-devs.next.
-- PMM
prev parent reply other threads:[~2013-06-03 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 15:32 [Qemu-devel] [PATCH V2 0/2] Fix memory migration for exynos 4210 SoC Igor Mitsyanko
2013-05-10 15:33 ` [Qemu-devel] [PATCH V2 1/2] hw/arm/exynos4210.c: convert chipid_and_omr to an mmio region Igor Mitsyanko
2013-05-10 15:33 ` [Qemu-devel] [PATCH V2 2/2] exynos4210.c: register rom_mem for memory migration Igor Mitsyanko
2013-06-03 15:05 ` 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=CAFEAcA8CWf7x_34C_f_hjv4TAS+6tsf_uAyUcyfGo+rzb2+eCA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=i.mitsyanko@gmail.com \
--cc=paul@codesourcery.com \
--cc=pbonzini@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).