qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCHv5 0/2] qemu: properties for feature compatibility
Date: Mon, 04 Jan 2010 16:56:35 +0100	[thread overview]
Message-ID: <4B420FB3.2090309@redhat.com> (raw)
In-Reply-To: <20100104153642.GA13809@redhat.com>

On 01/04/10 16:36, Michael S. Tsirkin wrote:
> Here's what I came up with for solving the problem of differences in
> features in virtio between 0.12 and 0.11.  This also enables migration
> between different backends, e.g.  between host where tap supports virtio
> net header and where it does not: management just needs to set features
> appropriately.

Looks good to me now.

Acked-by: Gerd Hoffmann <kraxel@redhat.com>

cheers,
   Gerd

      reply	other threads:[~2010-01-04 15:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-04 15:36 [Qemu-devel] [PATCHv5 0/2] qemu: properties for feature compatibility Michael S. Tsirkin
2010-01-04 15:56 ` Gerd Hoffmann [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=4B420FB3.2090309@redhat.com \
    --to=kraxel@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).