All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@gnu.org>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Jason Wang <jasowang@redhat.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] RFC: net/slirp: link with libslirp
Date: Sat, 9 Feb 2019 14:17:47 +0100	[thread overview]
Message-ID: <20190209131747.vy4sc34f6kbkvio2@function> (raw)
In-Reply-To: <20190208181226.24052-1-marcandre.lureau@redhat.com>

Marc-André Lureau, le ven. 08 févr. 2019 19:12:26 +0100, a ecrit:
> Once libslirp has received its first release, we can link with the
> external libslirp library.
> 
> The migration data should be compatible with current and older qemu
> versions (same compatibility as today). See "slirp: add state
> saving/loading" patch. However, the content should be treated as a
> blob, as the format may change eventually in the future.
> 
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>

Reviewed-by: Samuel Thibault <samuel.thibault@ens-lyon.org>

Thanks so much for all this work :)

  parent reply	other threads:[~2019-02-09 13:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08 18:12 [Qemu-devel] [PATCH 1/1] RFC: net/slirp: link with libslirp Marc-André Lureau
2019-02-08 21:56 ` Philippe Mathieu-Daudé
2019-02-09 13:17 ` Samuel Thibault [this message]
2019-02-10 21:37 ` Peter Maydell
2019-02-11 10:49   ` Marc-André Lureau
2019-02-11 11:09 ` Daniel P. Berrangé
2019-02-11 11:34   ` Marc-André Lureau
2019-02-11 11:41     ` Daniel P. Berrangé
2019-02-11 22:22     ` Samuel Thibault
2019-02-12 10:31       ` Daniel P. Berrangé
2019-02-12 10:43         ` Dr. David Alan Gilbert

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=20190209131747.vy4sc34f6kbkvio2@function \
    --to=samuel.thibault@gnu.org \
    --cc=dgilbert@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=jasowang@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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.