From: Anup Patel <anup@brainfault.org>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: Atish Patra <atish.patra@wdc.com>,
linux-riscv <linux-riscv@lists.infradead.org>,
Alistair Francis <Alistair.Francis@wdc.com>,
Damien Le Moal <Damien.LeMoal@wdc.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: Experimental branch
Date: Fri, 1 Nov 2019 00:12:17 +0530 [thread overview]
Message-ID: <CAAhSdy3Y1W_8Uu00F66jVM=ObFouxw1C_z4-MVkLh0+s5Wx3HQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1910311101480.23683@viisi.sifive.com>
On Thu, Oct 31, 2019 at 11:41 PM Paul Walmsley <paul.walmsley@sifive.com> wrote:
>
>
> Hi,
>
> There is now an "experimental" branch on the RISC-V kernel git tree:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/log/?h=experimental
>
> This branch will contain patches that have been posted to the list which
> are getting close to being in shape, but which are not yet ready for
> merging. It's an unstable branch, so don't base any patch submissions on
> it. The intention is to make it easier for folks to see what's upcoming
> in the distant future, beyond what's been queued for submission to Linus.
> This branch will receive very little testing to start, but this will
> improve over time as our automated testing improves.
>
> Right now the experimental branch contains the following patches:
>
> - Steven Price's generic page table dumping code (not yet in mainline, but
> looks close)
> - Zong Li's page table dumping code for RISC-V (based on Steven's generic
> page table dumper patches)
> - Anup Patel's KVM patches (waiting for the hypervisor specification to
> exit draft status, and for reviews and testing)
You can drop the KVM RISC-V patches from your experimental branch.
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.
Regards,
Anup
>
> but we expect patch sets to be added and removed quite frequently.
>
>
> regards,
>
> - Paul
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-10-31 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 18:11 Experimental branch Paul Walmsley
2019-10-31 18:42 ` Anup Patel [this message]
2019-10-31 19:29 ` Paul Walmsley
2019-11-18 10:50 ` Andreas Schwab
2019-11-23 2:47 ` Paul Walmsley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAhSdy3Y1W_8Uu00F66jVM=ObFouxw1C_z4-MVkLh0+s5Wx3HQ@mail.gmail.com' \
--to=anup@brainfault.org \
--cc=Alistair.Francis@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=atish.patra@wdc.com \
--cc=linux-riscv@lists.infradead.org \
--cc=paul.walmsley@sifive.com \
--cc=pbonzini@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).