Stephen, when we are at it: can you also add branch master of git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git (probably after the kvm/master thing) A good name might be kvms390-fixes This will contain fixes for kvm on s390 targeted for the current release. Usually this branch will be merged in Paolos kvm/master which will then go to Linus As contact please use "Christian Borntraeger <borntraeger@xxxxxxxxxx>" "Cornelia Huck <cohuck@xxxxxxxxxx>" kvm@xxxxxxxxxxxxxxx linux-s390@xxxxxxxxxxxxxxx Thanks a lot Christian On 11/27/2017 10:24 PM, Stephen Rothwell wrote: > 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. >
