From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Ilya Maximets <i.maximets@samsung.com>
Cc: mdroth@linux.vnet.ibm.com, qemu-devel <qemu-devel@nongnu.org>,
qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 00/97] Patch Round-up for stable 3.0.1, freeze on 2019-04-08
Date: Tue, 9 Apr 2019 09:59:14 +0100 [thread overview]
Message-ID: <20190409085913.GB2964@work-vm> (raw)
In-Reply-To: <c138abfe-61fd-6e04-8900-2ba2a24073de@samsung.com>
* Ilya Maximets (i.maximets@samsung.com) wrote:
> > 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")
>
> ?
OK with me.
Dave
> Best regards, Ilya Maximets.
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
WARNING: multiple messages have this Message-ID (diff)
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Ilya Maximets <i.maximets@samsung.com>
Cc: qemu-stable@nongnu.org, mdroth@linux.vnet.ibm.com,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 00/97] Patch Round-up for stable 3.0.1, freeze on 2019-04-08
Date: Tue, 9 Apr 2019 09:59:14 +0100 [thread overview]
Message-ID: <20190409085913.GB2964@work-vm> (raw)
Message-ID: <20190409085914.DXb9dmh9cLtBoidlgBMzFgq_tXHTCpoTGsZ21Xozcpw@z> (raw)
In-Reply-To: <c138abfe-61fd-6e04-8900-2ba2a24073de@samsung.com>
* Ilya Maximets (i.maximets@samsung.com) wrote:
> > 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")
>
> ?
OK with me.
Dave
> Best regards, Ilya Maximets.
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2019-04-09 8:59 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 ` [Qemu-devel] [PATCH 00/97] Patch Round-up for stable 3.0.1, freeze on 2019-04-08 Ilya Maximets
2019-04-08 12:33 ` Ilya Maximets
2019-04-09 8:59 ` Dr. David Alan Gilbert [this message]
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=20190409085913.GB2964@work-vm \
--to=dgilbert@redhat.com \
--cc=i.maximets@samsung.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 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).