From: Pavel Fedin <p.fedin@samsung.com>
To: 'Shannon Zhao' <shannon.zhao@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 0/3] Introduce eventfd support for virtio-mmio
Date: Thu, 07 May 2015 14:45:24 +0300 [thread overview]
Message-ID: <017e01d088bb$4e6ad330$eb407990$@samsung.com> (raw)
In-Reply-To: <554B488E.5000307@linaro.org>
Hello!
> Have you noticed below thread? This thread is based on the patchset from
Ying-
> Shiuan Pan.
>
> http://lists.gnu.org/archive/html/qemu-devel/2014-11/msg00594.html
Yes, of course. Actually my set is based on that one, it's just updated
against current master and improved a little bit. In v1 series cover letter
i wrote about that, just for v2 i decided not to retype the whole intro.
Perhaps that was a bad idea.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-05-07 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 10:46 [Qemu-devel] [PATCH v3 0/3] Introduce eventfd support for virtio-mmio Pavel Fedin
2015-05-07 11:12 ` Shannon Zhao
2015-05-07 11:45 ` Pavel Fedin [this message]
2015-05-07 14:39 ` 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='017e01d088bb$4e6ad330$eb407990$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhao@linaro.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).