On Wed, Sep 18, 2013 at 01:04:01PM +1000, Alexey Kardashevskiy wrote: > On 09/05/2013 04:07 PM, Paolo Bonzini wrote: > > Il 05/09/2013 05:16, Alexey Kardashevskiy ha scritto: > >>>>>> Sorry for my ignorance, but this is The Kernel, it is already there, broken > >>>>>> or not, even if it is broken, qemu cannot stay isolated, no? > >>>>>> This is a mechanical change, no more. > >>>> > >>>> It's a matter of keeping things bisectable. If we can detect a > >>>> breakage, we can first work around it, and then apply the header update. > >>>> And if we don't detect it, maintainers usually send pull requests when > >>>> they have time to work on breakage caused by their patches. > >> > >> I can see the discussion but I do not see if anyone is going to pull this > >> through any tree. Please, somebody, pull. Thanks. > > > > It will go in through the KVM tree, probably sometime next week. > > > It is pretty impressive how such a trivial patch is still on its way to the > upstream :) > It was applied long time ago https://git.kernel.org/cgit/virt/kvm/qemu-kvm.git/commit/?h=uq/master&id=8c409e659bc1373fab49a277bb5dc71babb73551 Sync with qemu.git does not happen after every patch though. If you are working on kvm parts using qemu-kvm.git uq/master branch will make sure that you are working on most up to date kvm bits. If you work depends on something that is not in qemu-kvm.git then let kvm maintainers know and we will send pull request to Anthony earlier. -- Gleb. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
