[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72=hvS6KxxkLocFOrU4E4pNi=y4OuJLm3iSiPGmi5B178Q@mail.gmail.com>
Date: Mon, 6 Mar 2023 20:28:47 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: gary@...yguo.net, 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, 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 Mon, Mar 6, 2023 at 8:18 PM Palmer Dabbelt <palmer@...belt.com> wrote:
>
> It's time for the next release. IIUC there were some authorship issues
> here, did you guys want to re-spin this with those sorted out? I can
> give it a shot if you want, but I'm probably as likely to screw it up as
> anyone else...
No problem on my side, and either way is fine! Thanks!
I think what is important is that Gary is aware and agrees.
Gary: do you prefer to be the main author or the `Co-developed-by` author here?
Cheers,
Miguel
Powered by blists - more mailing lists