Re: Experimental branch

From: Paul Walmsley <paul.walmsley@sifive.com>
To: Anup Patel <anup@brainfault.org>
Cc: Damien Le Moal <Damien.LeMoal@wdc.com>,
	linux-kernel@vger.kernel.org, Atish Patra <atish.patra@wdc.com>,
	Alistair Francis <Alistair.Francis@wdc.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: Experimental branch
Date: Thu, 31 Oct 2019 12:29:49 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.21.9999.1910311223050.16921@viisi.sifive.com> (raw)
In-Reply-To: <CAAhSdy3Y1W_8Uu00F66jVM=ObFouxw1C_z4-MVkLh0+s5Wx3HQ@mail.gmail.com>

On Fri, 1 Nov 2019, Anup Patel wrote:

> You can drop the KVM RISC-V patches from your experimental branch.

We're not only doing it for you ;-)

> We are already maintaining KVM RISC-V patches (and dependent patches)
> in the official KVM RISC-V gitrepo at: https://github.com/kvm-riscv/linux.git
> 
> All KVM RISC-V related work will go through above mentioned gitrepo
> in-future. This gitrepo is co-maintained by me and Atish.

It's great that you guys have your own git repository for KVM patch 
development!

For upstreaming, all of the RISC-V KVM changes under arch/riscv need to go 
up via the arch/riscv maintainers to ensure a coherent maintenance 
approach across arch/riscv.  We may work out something with Paolo in the 
future.

thanks,

- Paul

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv