From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Brijesh Singh <brijesh.singh@amd.com>
Cc: Thomas.Lendacky@amd.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 for-2.12] tap: set vhostfd passed from qemu cli to non-blocking
Date: Mon, 21 May 2018 11:01:19 +0800 [thread overview]
Message-ID: <8e0a275f-18f3-49b9-b50a-207b443f4fd6@redhat.com> (raw)
In-Reply-To: <20180517180833-mutt-send-email-mst@kernel.org>
On 2018年05月17日 23:08, Michael S. Tsirkin wrote:
> On Thu, May 17, 2018 at 09:54:40AM -0500, Brijesh Singh wrote:
>> Hi Michael and Jason,
>>
>> Looks like this patch was not included in any of your pull request hence it
>> didn't made into 2.12. Can you please include this patch in your next pull
>> request?
>>
>> ~ Brijesh
>
> I reviewed.
> Jason?
> Cc stable I guess ...
Yes. Applied.
Thanks
prev parent reply other threads:[~2018-05-21 3:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 18:51 [Qemu-devel] [PATCH v2 for-2.12] tap: set vhostfd passed from qemu cli to non-blocking Brijesh Singh
2018-04-08 3:53 ` Michael S. Tsirkin
2018-05-17 14:54 ` Brijesh Singh
2018-05-17 15:08 ` Michael S. Tsirkin
2018-05-21 3:01 ` Jason Wang [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=8e0a275f-18f3-49b9-b50a-207b443f4fd6@redhat.com \
--to=jasowang@redhat.com \
--cc=Thomas.Lendacky@amd.com \
--cc=brijesh.singh@amd.com \
--cc=mst@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).