All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ilya Maximets <i.maximets@samsung.com>
To: mdroth@linux.vnet.ibm.com
Cc: qemu-devel <qemu-devel@nongnu.org>,
	qemu-stable@nongnu.org, dgilbert@redhat.com
Subject: [Qemu-devel]  [PATCH 00/97] Patch Round-up for stable 3.0.1, freeze on 2019-04-08
Date: Mon, 8 Apr 2019 15:33:39 +0300	[thread overview]
Message-ID: <c138abfe-61fd-6e04-8900-2ba2a24073de@samsung.com> (raw)
In-Reply-To: CGME20190408123341eucas1p2add7886160b2b66912413defd4544d1f@eucas1p2.samsung.com

> Hi everyone,                                                                    
>                           
> 
> The following new patches are queued for QEMU stable v3.0.1:
> 
>   https://github.com/mdroth/qemu/commits/stable-3.0-staging
> 
> The release is planned for 2019-04-11:
> 
>   https://wiki.qemu.org/Planning/3.0
> 
> Please respond here or CC address@hidden on any patches you
> think should be included in the release.
> 
> Note that this update falls outside the normal stable release support
> window (~1 development cycle), but is being release now since it was
> delayed from its intended release date.
> 
> Thanks!
> 

[...]

> 
> Ilya Maximets (1):
>       migration: Stop postcopy fault thread before notifying

Hi.

Sorry for late response, but what about following two patches:

  c4f753859ae6 ("vhost-user: Fix userfaultfd leak")
  5ce43896e167 ("vhost-user: Don't ask for reply on postcopy mem table set")

?

Best regards, Ilya Maximets.

WARNING: multiple messages have this Message-ID (diff)
From: Ilya Maximets <i.maximets@samsung.com>
To: mdroth@linux.vnet.ibm.com
Cc: qemu-devel <qemu-devel@nongnu.org>,
	dgilbert@redhat.com, qemu-stable@nongnu.org
Subject: [Qemu-devel]  [PATCH 00/97] Patch Round-up for stable 3.0.1, freeze on 2019-04-08
Date: Mon, 8 Apr 2019 15:33:39 +0300	[thread overview]
Message-ID: <c138abfe-61fd-6e04-8900-2ba2a24073de@samsung.com> (raw)
Message-ID: <20190408123339.spSeGMxRhx1GR-rylus-ZiXOC8NOJXeobDKc7xLvjgc@z> (raw)
In-Reply-To: CGME20190408123341eucas1p2add7886160b2b66912413defd4544d1f@eucas1p2.samsung.com

> Hi everyone,                                                                    
>                           
> 
> The following new patches are queued for QEMU stable v3.0.1:
> 
>   https://github.com/mdroth/qemu/commits/stable-3.0-staging
> 
> The release is planned for 2019-04-11:
> 
>   https://wiki.qemu.org/Planning/3.0
> 
> Please respond here or CC address@hidden on any patches you
> think should be included in the release.
> 
> Note that this update falls outside the normal stable release support
> window (~1 development cycle), but is being release now since it was
> delayed from its intended release date.
> 
> Thanks!
> 

[...]

> 
> Ilya Maximets (1):
>       migration: Stop postcopy fault thread before notifying

Hi.

Sorry for late response, but what about following two patches:

  c4f753859ae6 ("vhost-user: Fix userfaultfd leak")
  5ce43896e167 ("vhost-user: Don't ask for reply on postcopy mem table set")

?

Best regards, Ilya Maximets.


       reply	other threads:[~2019-04-08 12:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20190408123341eucas1p2add7886160b2b66912413defd4544d1f@eucas1p2.samsung.com>
2019-04-08 12:33 ` Ilya Maximets [this message]
2019-04-08 12:33   ` [Qemu-devel] [PATCH 00/97] Patch Round-up for stable 3.0.1, freeze on 2019-04-08 Ilya Maximets
2019-04-09  8:59   ` Dr. David Alan Gilbert
2019-04-09  8:59     ` Dr. David Alan Gilbert
2019-04-01 20:58 Michael Roth
2019-04-04 22:31 ` Philippe Mathieu-Daudé
2019-04-04 22:31   ` Philippe Mathieu-Daudé
2019-04-05 20:28   ` Michael Roth
2019-04-05 20:28     ` Michael Roth

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=c138abfe-61fd-6e04-8900-2ba2a24073de@samsung.com \
    --to=i.maximets@samsung.com \
    --cc=dgilbert@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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 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.