From: Pavel Fedin <p.fedin@samsung.com>
To: 'Peter Maydell' <peter.maydell@linaro.org>
Cc: 'QEMU Developers' <qemu-devel@nongnu.org>
Subject: [Qemu-devel] PING: RE: [PATCH RFC V3 1/4] Use Aff1 with mpidr This is an improved and KVM-aware alternative to
Date: Thu, 11 Jun 2015 10:46:18 +0300 [thread overview]
Message-ID: <000001d0a41a$b3f4bc50$1bde34f0$@samsung.com> (raw)
Hi Peter!
> Hi. I think this patch largely makes sense, but I have some comments
> below. If you want to fix these and resend as a standalone patch
> I'm happy to apply that.
How are things going? I have resent v4 of this on the very same day, and got no reaction from you since then. My vGICv3 implementation is waiting. It even has support for proposed in-kernel ITS emulation: http://www.mail-archive.com/kvm@vger.kernel.org/msg116057.html
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next reply other threads:[~2015-06-11 7:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 7:46 Pavel Fedin [this message]
2015-06-11 8:49 ` [Qemu-devel] PING: RE: [PATCH RFC V3 1/4] Use Aff1 with mpidr This is an improved and KVM-aware alternative to Peter Maydell
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='000001d0a41a$b3f4bc50$1bde34f0$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=peter.maydell@linaro.org \
--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).