From: Gary Guo <gary@garyguo.net>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Conor Dooley <conor.dooley@microchip.com>,
linux-riscv@lists.infradead.org, Conor Dooley <conor@kernel.org>,
ojeda@kernel.org, alex.gaynor@gmail.com, wedsonaf@gmail.com,
boqun.feng@gmail.com, bjorn3_gh@protonmail.com, corbet@lwn.net,
Paul Walmsley <paul.walmsley@sifive.com>,
nathan@kernel.org, ndesaulniers@google.com, trix@redhat.com,
rust-for-linux@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [RFC 0/2] RISC-V: enable rust
Date: Tue, 7 Mar 2023 02:20:37 +0000 [thread overview]
Message-ID: <20230307022037.6528b6d1.gary@garyguo.net> (raw)
In-Reply-To: <CANiq72=hvS6KxxkLocFOrU4E4pNi=y4OuJLm3iSiPGmi5B178Q@mail.gmail.com>
On Mon, 6 Mar 2023 20:28:47 +0100
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> wrote:
> On Mon, Mar 6, 2023 at 8:18 PM Palmer Dabbelt <palmer@dabbelt.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?
Co-developed-by is fine.
Best,
Gary
WARNING: multiple messages have this Message-ID (diff)
From: Gary Guo <gary@garyguo.net>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Conor Dooley <conor.dooley@microchip.com>,
linux-riscv@lists.infradead.org, Conor Dooley <conor@kernel.org>,
ojeda@kernel.org, alex.gaynor@gmail.com, wedsonaf@gmail.com,
boqun.feng@gmail.com, bjorn3_gh@protonmail.com, corbet@lwn.net,
Paul Walmsley <paul.walmsley@sifive.com>,
nathan@kernel.org, ndesaulniers@google.com, trix@redhat.com,
rust-for-linux@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [RFC 0/2] RISC-V: enable rust
Date: Tue, 7 Mar 2023 02:20:37 +0000 [thread overview]
Message-ID: <20230307022037.6528b6d1.gary@garyguo.net> (raw)
In-Reply-To: <CANiq72=hvS6KxxkLocFOrU4E4pNi=y4OuJLm3iSiPGmi5B178Q@mail.gmail.com>
On Mon, 6 Mar 2023 20:28:47 +0100
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> wrote:
> On Mon, Mar 6, 2023 at 8:18 PM Palmer Dabbelt <palmer@dabbelt.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?
Co-developed-by is fine.
Best,
Gary
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-03-07 2:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 13:36 [RFC 0/2] RISC-V: enable rust Conor Dooley
2023-02-24 13:36 ` Conor Dooley
2023-02-24 13:36 ` [RFC 1/2] scripts: generate_rust_target: enable building on RISC-V Conor Dooley
2023-02-24 13:36 ` [RFC 2/2] RISC-V: enable building the 64-bit kernels with rust support Conor Dooley
2023-02-24 13:39 ` Conor Dooley
2023-02-24 20:42 ` [RFC 0/2] RISC-V: enable rust Miguel Ojeda
2023-02-24 20:42 ` Miguel Ojeda
2023-02-24 21:00 ` Conor Dooley
2023-02-24 21:00 ` Conor Dooley
2023-02-24 22:20 ` Miguel Ojeda
2023-02-24 22:20 ` Miguel Ojeda
2023-02-24 22:32 ` Conor Dooley
2023-02-24 22:32 ` Conor Dooley
2023-02-25 8:20 ` Miguel Ojeda
2023-02-25 8:20 ` Miguel Ojeda
2023-02-24 21:31 ` Palmer Dabbelt
2023-02-24 21:31 ` Palmer Dabbelt
2023-02-24 22:38 ` Miguel Ojeda
2023-02-24 22:38 ` Miguel Ojeda
2023-02-24 23:18 ` Palmer Dabbelt
2023-02-24 23:18 ` Palmer Dabbelt
2023-02-25 8:37 ` Miguel Ojeda
2023-02-25 8:37 ` Miguel Ojeda
2023-03-06 19:18 ` Palmer Dabbelt
2023-03-06 19:18 ` Palmer Dabbelt
2023-03-06 19:26 ` Conor Dooley
2023-03-06 19:26 ` Conor Dooley
2023-03-06 19:28 ` Miguel Ojeda
2023-03-06 19:28 ` Miguel Ojeda
2023-03-07 2:20 ` Gary Guo [this message]
2023-03-07 2:20 ` Gary Guo
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=20230307022037.6528b6d1.gary@garyguo.net \
--to=gary@garyguo.net \
--cc=alex.gaynor@gmail.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=trix@redhat.com \
--cc=wedsonaf@gmail.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.