From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/5] pc, virtio: fixes
Date: Fri, 3 Aug 2018 21:14:34 +0300 [thread overview]
Message-ID: <20180803211129-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAFEAcA9r4K9qgFFqvRKqTFMUowyAAEV=QZEnhk3eheQRodbnvA@mail.gmail.com>
On Fri, Aug 03, 2018 at 11:45:36AM +0100, Peter Maydell wrote:
> On 3 August 2018 at 10:27, Michael S. Tsirkin <mst@redhat.com> wrote:
> > Please consider for 3.0 if there is another rc.
> >
> > The following changes since commit f7502360397d291be04bc040e9f96c92ff2d8030:
> >
> > Update version for v3.0.0-rc3 release (2018-07-31 19:30:17 +0100)
> >
> > are available in the Git repository at:
> >
> > git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_upstream
> >
> > for you to fetch changes up to 1c707d6990eaf3db0c9dc4557bba5458977e9f8d:
> >
> > tests/acpi: update tables after memory hotplug changes (2018-08-03 11:35:21 +0300)
> >
> > ----------------------------------------------------------------
> > pc, virtio: fixes
> >
> > A couple of last minute fixes.
> >
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> >
> > ----------------------------------------------------------------
> > Dou Liyang (2):
> > hw/acpi-build: Add a check for memory-less NUMA nodes
> > tests/acpi-test: update ACPI tables test blobs
This fixes a regression but from an older release.
> >
> > Igor Mammedov (1):
> > pc: acpi: fix memory hotplug regression by reducing stub SRAT entry size
This fixes a regression from 2.12.
> > Michael S. Tsirkin (1):
> > tests/acpi: update tables after memory hotplug changes
This will have to be re-done if we pick this but drop two other fixes.
> >
> > Tiwei Bie (1):
> > vhost: check region type before casting
Not a regression but an obvious fix.
>
> Can you clarify which of these are regressions from 2.12, please?
> At this point in the release cycle I only want to apply fixes
> for regressions. (Test only updates might also be OK, but I
> need more information than just the commit message subject line.)
>
> thanks
> -- PMM
I'll push a variant with just the two patches fixing
regression from 2.12 soon.
--
MST
next prev parent reply other threads:[~2018-08-03 18:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 9:27 [Qemu-devel] [PULL 0/5] pc, virtio: fixes Michael S. Tsirkin
2018-08-03 9:27 ` [Qemu-devel] [PULL 1/5] vhost: check region type before casting Michael S. Tsirkin
2018-08-03 9:27 ` [Qemu-devel] [PULL 2/5] hw/acpi-build: Add a check for memory-less NUMA nodes Michael S. Tsirkin
2018-08-03 9:28 ` [Qemu-devel] [PULL 3/5] tests/acpi-test: update ACPI tables test blobs Michael S. Tsirkin
2018-08-03 9:28 ` [Qemu-devel] [PULL 4/5] pc: acpi: fix memory hotplug regression by reducing stub SRAT entry size Michael S. Tsirkin
2018-08-03 9:28 ` [Qemu-devel] [PULL 5/5] tests/acpi: update tables after memory hotplug changes Michael S. Tsirkin
2018-08-03 10:45 ` [Qemu-devel] [PULL 0/5] pc, virtio: fixes Peter Maydell
2018-08-03 18:14 ` Michael S. Tsirkin [this message]
2018-08-06 8:37 ` Peter Maydell
2018-08-06 9:47 ` Peter Maydell
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=20180803211129-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--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).