[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72ndkF0JM1kV=ewnO4uGirDowHDGLkhvjQgtLnuPEk_hTQ@mail.gmail.com>
Date: Sat, 25 Feb 2023 09:37:29 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Palmer Dabbelt <palmer@...belt.com>
Cc: Conor Dooley <conor.dooley@...rochip.com>,
linux-riscv@...ts.infradead.org, Conor Dooley <conor@...nel.org>,
ojeda@...nel.org, alex.gaynor@...il.com, wedsonaf@...il.com,
boqun.feng@...il.com, gary@...yguo.net, bjorn3_gh@...tonmail.com,
corbet@....net, Paul Walmsley <paul.walmsley@...ive.com>,
nathan@...nel.org, ndesaulniers@...gle.com, trix@...hat.com,
rust-for-linux@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, llvm@...ts.linux.dev
Subject: Re: [RFC 0/2] RISC-V: enable rust
On Sat, Feb 25, 2023 at 12:18 AM Palmer Dabbelt <palmer@...belt.com> wrote:
>
> Works for me.
>
> I've got a few other things in the pipeline for this merge window so
> this probably won't make it, but I'll dig in after that. We've got a
> bunch of Rust-types floating around Rivos as well, so with any luck
> someone else will have some time to poke around. Having a full cycle in
> linux-next is probably the right way to go for this sort of thing
> anyway, as it's likely to shake out some long-tail issues.
Thanks a lot! That would be great.
At least from our side, no rush. In fact, we are letting users (or
arch maintainers) to request/submit the architectures themselves as
they need/want them.
Cheers,
Miguel
Powered by blists - more mailing lists