Re: new KVM branch for linux-next

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

 



Hi Paolo,

On Mon, 27 Nov 2017 17:44:24 +0100 Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote:
>
> could you please add refs/heads/master of
> git://git.kernel.org/pub/scm/virt/kvm/kvm.git to linux-next, right
> before the existing refs/heads/linux-next tree?

Added from today with you and the KVM mailing list as contacts.

Can you tell me what this tree is for?  Will it only contain bug fixes
for he current release?

BTW, the contacts for the "kvm" tree are Marcelo Tosatti
<mtosatti@xxxxxxxxxx>, Gleb Natapov <gleb@xxxxxxxxxx>, KVM
<kvm@xxxxxxxxxxxxxxx> - are they all still appropriate?

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
        Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@xxxxxxxxxxxxxxxx



[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