qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 00/113] Patch Round-up for stable 2.11.2, freeze


From: Michael Roth
Subject: Re: [Qemu-devel] [PATCH 00/113] Patch Round-up for stable 2.11.2, freeze on 2018-06-22
Date: Wed, 20 Jun 2018 15:41:24 -0500
User-agent: alot/0.6

Quoting Cornelia Huck (2018-06-19 02:42:48)
> On Mon, 18 Jun 2018 20:41:26 -0500
> Michael Roth <address@hidden> wrote:
> 
> > Hi everyone,
> > 
> > The following new patches are queued for QEMU stable v2.11.2:
> > 
> >   https://github.com/mdroth/qemu/commits/stable-2.11-staging
> > 
> > The release is planned for 2018-06-22:
> > 
> >   https://wiki.qemu.org/Planning/2.11
> > 
> > Please respond here or CC address@hidden on any patches you
> > think should be included in the release.
> > 
> > Thanks!
> > 
> > ----------------------------------------------------------------
> > 
> > The following changes since commit 7c1beb52ed86191d9e965444d934adaa2531710f:
> > 
> >   Update version for 2.11.1 release (2018-02-14 14:41:05 -0600)
> > 
> > are available in the git repository at:
> > 
> >   git://github.com/mdroth/qemu.git 
> > 
> > for you to fetch changes up to acb3571f90885a2e206044b3bdc8d1dd2a0389c0:
> > 
> >   arm_gicv3_kvm: kvm_dist_get/put_priority: skip the registers banked by 
> > GICR_IPRIORITYR (2018-06-16 07:47:00 -0500)
> > 
> > ----------------------------------------------------------------
> 
> Hi Michael,
> 
> as this series includes some s390-ccw bios patches, it needs a rebuild
> of the s390-ccw bios as well, probably on top of your stable branch.
> (IIRC we have extra patches on master, so you probably don't want to
> cherry-pick the latest rebuild from there.). Let me know if one of us
> should provide a rebuild.
> 

Thanks Cornelia, I hadn't realized that. I think rebuild from one of the
maintainers would definitely be preferable. We'd also want the corresponding
patches for pc-bios/s390-ccw reflected in the 2.11.x tree. If you or
another maintainer could put together a branch with those I can merge
those in directly.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]