All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>,
	dgilbert@redhat.com, Alexander Graf <agraf@suse.de>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH 1/2] virtio: allow per-device-class legacy features
Date: Fri, 4 Nov 2016 12:32:06 +0100	[thread overview]
Message-ID: <20161104123206.16e87b93.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <1478257275-30365-2-git-send-email-mst@redhat.com>

On Fri, 4 Nov 2016 13:01:37 +0200
"Michael S. Tsirkin" <mst@redhat.com> wrote:

> Legacy features are those that transitional devices only
> expose on the legacy interface.
> Allow different ones per device class.
> 
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
>  include/hw/virtio/virtio.h | 5 +++++
>  hw/s390x/virtio-ccw.c      | 4 +++-
>  hw/virtio/virtio-pci.c     | 4 +++-
>  hw/virtio/virtio.c         | 2 ++
>  4 files changed, 13 insertions(+), 2 deletions(-)

Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>

  reply	other threads:[~2016-11-04 11:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-04 11:01 [Qemu-devel] [PATCH 0/2] virtio-net: spec compatibility fix Michael S. Tsirkin
2016-11-04 11:01 ` [Qemu-devel] [PATCH 1/2] virtio: allow per-device-class legacy features Michael S. Tsirkin
2016-11-04 11:32   ` Cornelia Huck [this message]
2016-11-07  9:11   ` Jason Wang
2016-11-04 11:01 ` [Qemu-devel] [PATCH 2/2] virtio-net: mark VIRTIO_NET_F_GSO as legacy Michael S. Tsirkin
2016-11-04 11:37   ` Cornelia Huck
2016-11-07  9:11   ` Jason Wang
2016-11-07 15:38   ` Dr. David Alan Gilbert
2016-11-07 19:43     ` Halil Pasic
2016-11-07 19:25   ` Halil Pasic

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=20161104123206.16e87b93.cornelia.huck@de.ibm.com \
    --to=cornelia.huck@de.ibm.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=dgilbert@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.