From: Stefan Hajnoczi <stefanha@gmail.com>
To: Jason Wang <jasowang@redhat.com>
Cc: qemu-devel@nongnu.org, aliguori@amazon.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH] virtio-net: correctly advertise host features
Date: Thu, 13 Nov 2014 11:30:25 +0000 [thread overview]
Message-ID: <20141113113025.GO7462@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1415858145-23461-1-git-send-email-jasowang@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 297 bytes --]
On Thu, Nov 13, 2014 at 01:55:45PM +0800, Jason Wang wrote:
> We should not advertise the feature that depends on ctrl vq is it was not
> enabled. And not advertise the VIRTIO_NET_F_CTRL_RX_EXTRA is
s/is/if/
> VIRTIO_NET_F_CTRL_RX is not enabled.
s/is/it/
These can be fixed up while merging.
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2014-11-13 11:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 5:55 [Qemu-devel] [PATCH] virtio-net: correctly advertise host features Jason Wang
2014-11-13 11:30 ` Stefan Hajnoczi [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=20141113113025.GO7462@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=aliguori@amazon.com \
--cc=jasowang@redhat.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).