From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Damien Le Moal <Damien.LeMoal@wdc.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Anup Patel <anup@brainfault.org>,
linux-riscv <linux-riscv@lists.infradead.org>,
Anup Patel <Anup.Patel@wdc.com>,
Palmer Dabbelt <palmerdabbelt@google.com>,
Palmer Dabbelt <palmer@dabbelt.com>
Subject: Re: arch/riscv/staging
Date: Fri, 28 May 2021 11:24:39 +0200 [thread overview]
Message-ID: <YLC211VUeTrUdo3v@kroah.com> (raw)
In-Reply-To: <CH2PR04MB70782F16D88C700AB621D1B6E7229@CH2PR04MB7078.namprd04.prod.outlook.com>
On Fri, May 28, 2021 at 08:58:07AM +0000, Damien Le Moal wrote:
> On 2021/05/28 17:53, Greg Kroah-Hartman wrote:
> > On Fri, May 28, 2021 at 10:29:16AM +0200, Paolo Bonzini wrote:
> >> On 28/05/21 03:06, Paul Walmsley wrote:
> >>> OK, well, maybe you and Damien can get together and spell out what you all
> >>> are concerned about regarding forks. Then we can see if there's anything
> >>> that should be done to address it.
> >>>
> >>> Right now the only fork risk that I can see is related to the architecture
> >>> itself.
> >>
> >> The risk is that improvements to KVM RISC-V are developed in forks rather
> >> than in a single git tree.
> >
> > Eventually they need to come back into the mainline tree, so that should
> > not be that big of an issue.
> >
> > If it is, again, get the spec finished, what is preventing that from
> > happening this week?
>
> We (kernel & riscv software developers) do not get to decide alone. RISC-V
> International specification group decides. And our input does not seem to have
> much effect on the completion timing. See this thread:
>
> https://lists.riscv.org/g/tech-privileged/topic/80346318#465
Ok, as it sounds like this isn't going anywhere until the spec group
gets their work done, you all should just wait as there's no real need
for any kernel code here either, given that there can't be any hardware
made until the spec is finished anyway.
thanks,
greg k-h
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2021-05-28 9:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 2:05 arch/riscv/staging Damien Le Moal
2021-05-21 2:08 ` arch/riscv/staging Damien Le Moal
2021-05-21 17:22 ` arch/riscv/staging Paul Walmsley
2021-05-22 3:05 ` arch/riscv/staging Anup Patel
2021-05-28 1:06 ` arch/riscv/staging Paul Walmsley
2021-05-28 8:29 ` arch/riscv/staging Paolo Bonzini
2021-05-28 8:53 ` arch/riscv/staging Greg Kroah-Hartman
2021-05-28 8:58 ` arch/riscv/staging Damien Le Moal
2021-05-28 9:24 ` Greg Kroah-Hartman [this message]
2021-05-28 9:37 ` arch/riscv/staging Paolo Bonzini
2021-05-28 10:59 ` arch/riscv/staging Greg Kroah-Hartman
2021-05-28 11:19 ` arch/riscv/staging Anup Patel
2021-05-28 11:45 ` arch/riscv/staging Paolo Bonzini
2021-05-28 11:28 ` arch/riscv/staging Paolo Bonzini
2021-05-28 11:35 ` arch/riscv/staging Greg Kroah-Hartman
2021-05-28 8:50 ` arch/riscv/staging Paolo Bonzini
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=YLC211VUeTrUdo3v@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Anup.Patel@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=anup@brainfault.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmerdabbelt@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.