kvm/next rebased

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

 



Hi all,

after Linus accepted Radim's "trimmed" pull request (which was very nice
of both of them, since it let 4.15 get GICv4), we've decided to move
guest-side UMIP to 4.16.

This is the current state of the tree:

- kvm/master is the trimmed pull request, and the bugfixes that were not
in the trimmed pull request will get there very soon (tomorrow evening
perhaps).  From there they'll get into linux-next and -rc2.

- kvm/next is currently at 4.15-rc1, and (as usual immediately after the
end of the merge window) it will include those bugfixes as soon as Linus
pulls kvm/master.  *The bugfixes that Radim dropped are not anymore in
kvm/next*.

- kvm/queue is the current state of the next 4.15-rc2 pull request, with
the guest-side UMIP patches on top.  kvm/queue was rebased too, but
there's nothing special in that.

This should minimize the rewriting of SHA-1 ids involved.  In
particular, all kvm/queue commits up to a63dd7480d8f ("Merge tag
'kvm-ppc-fixes-4.15-1'") should be stable.

Since we've had quite a few activity in the week immediately around the
4.14 release, my current guess is that kvm/next will stop rebasing
pretty early, maybe as soon as 4.15-rc2.

Thanks,

Paolo



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux