Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Thu, 31 Oct 2019 12:29:49 -0700 (PDT)
From:   Paul Walmsley <paul.walmsley@sifive.com>
To:     Anup Patel <anup@brainfault.org>
cc:     linux-riscv <linux-riscv@lists.infradead.org>,
        Atish Patra <atish.patra@wdc.com>,
        Paolo Bonzini <pbonzini@redhat.com>,
        Damien Le Moal <Damien.LeMoal@wdc.com>,
        Alistair Francis <Alistair.Francis@wdc.com>,
        linux-kernel@vger.kernel.org
Subject: Re: Experimental branch
In-Reply-To: <CAAhSdy3Y1W_8Uu00F66jVM=ObFouxw1C_z4-MVkLh0+s5Wx3HQ@mail.gmail.com>
Message-ID: <alpine.DEB.2.21.9999.1910311223050.16921@viisi.sifive.com>
References: <alpine.DEB.2.21.9999.1910311101480.23683@viisi.sifive.com> <CAAhSdy3Y1W_8Uu00F66jVM=ObFouxw1C_z4-MVkLh0+s5Wx3HQ@mail.gmail.com>
User-Agent: Alpine 2.21.9999 (DEB 301 2018-08-15)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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