linux-kernel - Re: Experimental branch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.21.9999.1910311223050.16921@viisi.sifive.com>
Date:   Thu, 31 Oct 2019 12:29:49 -0700 (PDT)
From:   Paul Walmsley <paul.walmsley@...ive.com>
To:     Anup Patel <anup@...infault.org>
cc:     linux-riscv <linux-riscv@...ts.infradead.org>,
        Atish Patra <atish.patra@....com>,
        Paolo Bonzini <pbonzini@...hat.com>,
        Damien Le Moal <Damien.LeMoal@....com>,
        Alistair Francis <Alistair.Francis@....com>,
        linux-kernel@...r.kernel.org
Subject: Re: Experimental branch

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