From: Alex Gaynor <alex.gaynor@gmail.com>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: "Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev, "Benno Lossin" <benno.lossin@proton.me>
Subject: Re: [PATCH] MAINTAINERS: add Benno Lossin as Rust reviewer
Date: Thu, 20 Apr 2023 16:32:37 -0600 [thread overview]
Message-ID: <CAFRnB2W_KSpUMJQXvzyOcR8XBUmO=Bx+hDZH_Se-QrMfyiKsgQ@mail.gmail.com> (raw)
In-Reply-To: <CAFRnB2VygPYBY7MbxoftzEtqs52YG5AN_EO72Nm1ukLWnApa=Q@mail.gmail.com>
My previous line was incorrect. Corrected:
Reviewed-by: Alex Gaynor <alex.gaynor@gmail.com>
On Wed, Apr 12, 2023 at 4:21 PM Alex Gaynor <alex.gaynor@gmail.com> wrote:
>
> Signed-off-by: Alex Gaynor <alex.gaynor@gmail.com>
>
> On Wed, Apr 12, 2023 at 6:18 PM Miguel Ojeda <ojeda@kernel.org> wrote:
> >
> > Benno has been involved with the Rust for Linux project for
> > the better part of a year now. He has been working on solving
> > the safe pinned initialization problem [1], which resulted in
> > the pin-init API patch series [2] that allows to reduce the
> > need for `unsafe` code in the kernel. He is also working on
> > the field projection RFC for Rust [3] to bring pin-init as
> > a language feature.
> >
> > His expertise with the language will be very useful to have
> > around in the future if Rust grows within the kernel, thus
> > add him to the `RUST` entry as reviewer.
> >
> > Link: https://rust-for-linux.com/the-safe-pinned-initialization-problem [1]
> > Link: https://lore.kernel.org/rust-for-linux/20230408122429.1103522-1-y86-dev@protonmail.com/ [2]
> > Link: https://github.com/rust-lang/rfcs/pull/3318 [3]
> > Cc: Benno Lossin <benno.lossin@proton.me>
> > Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
> > ---
> > MAINTAINERS | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 90abe83c02f3..bf9deaa4aa5a 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -18225,6 +18225,7 @@ M: Wedson Almeida Filho <wedsonaf@gmail.com>
> > R: Boqun Feng <boqun.feng@gmail.com>
> > R: Gary Guo <gary@garyguo.net>
> > R: Björn Roy Baron <bjorn3_gh@protonmail.com>
> > +R: Benno Lossin <benno.lossin@proton.me>
> > L: rust-for-linux@vger.kernel.org
> > S: Supported
> > W: https://github.com/Rust-for-Linux/linux
> >
> > base-commit: 09a9639e56c01c7a00d6c0ca63f4c7c41abe075d
> > --
> > 2.40.0
> >
>
>
> --
> All that is necessary for evil to succeed is for good people to do nothing.
--
All that is necessary for evil to succeed is for good people to do nothing.
next prev parent reply other threads:[~2023-04-20 22:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 22:18 [PATCH] MAINTAINERS: add Benno Lossin as Rust reviewer Miguel Ojeda
2023-04-12 22:21 ` Alex Gaynor
2023-04-20 22:32 ` Alex Gaynor [this message]
2023-04-21 22:46 ` Miguel Ojeda
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='CAFRnB2W_KSpUMJQXvzyOcR8XBUmO=Bx+hDZH_Se-QrMfyiKsgQ@mail.gmail.com' \
--to=alex.gaynor@gmail.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=patches@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--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 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).