All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Miguel Ojeda" <ojeda@kernel.org>
Cc: "Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Daniel Almeida" <daniel.almeida@collabora.com>,
	"Tamir Duberstein" <tamird@kernel.org>,
	"Onur Özkan" <work@onurozkan.dev>,
	rust-for-linux@vger.kernel.org
Subject: Re: [PATCH 3/4] MAINTAINERS: add Alexandre Courbot as Rust reviewer
Date: Fri, 12 Jun 2026 07:43:26 +0900	[thread overview]
Message-ID: <DJ6L0K01VI4J.1X1J16POP4JSY@nvidia.com> (raw)
In-Reply-To: <20260611055538.61425-3-ojeda@kernel.org>

On Thu Jun 11, 2026 at 2:55 PM JST, Miguel Ojeda wrote:
> Alexandre has been involved with the Rust for Linux project for more
> than a year now. He is one of the main contributors to Nova [1], the
> Rust driver for NVIDIA GPUs, and has authored core Rust infrastructure
> motivated by that work, such as the `num` module with the `Bounded`
> integer type, the `register!` and `bitfield!` macros, as well as
> improvements to abstractions like DMA.
>
> He maintains the nova-core driver, as well as the `RUST [NUM]`, `RUST
> [BITFIELD]` and `RUST [INTEROP]` entries. In addition, he has been very
> active reviewing Rust code in the mailing list.
>
> He also proposed and implemented the `int_lowest_highest_one` feature
> in the Rust standard library [2], which we should eventually use in
> the kernel.
>
> His experience maintaining a major Rust GPU driver and the abstractions
> it needs will be very useful to have around in the future. Thus add him
> to the `RUST` entry as reviewer.
>
> Link: https://rust-for-linux.com/nova-gpu-driver [1]
> Link: https://github.com/rust-lang/rust/issues/145203 [2]
> Signed-off-by: Miguel Ojeda <ojeda@kernel.org>

Being part of this community has been a formative experience, and a
genuine pleasure. Thank you Miguel for your role in building it!

Acked-by: Alexandre Courbot <acourbot@nvidia.com>

  parent reply	other threads:[~2026-06-11 22:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-11  5:55 [PATCH 1/4] MAINTAINERS: add Daniel Almeida as Rust reviewer Miguel Ojeda
2026-06-11  5:55 ` [PATCH 2/4] MAINTAINERS: add Tamir Duberstein " Miguel Ojeda
2026-06-11 18:54   ` Tamir Duberstein
2026-06-11  5:55 ` [PATCH 3/4] MAINTAINERS: add Alexandre Courbot " Miguel Ojeda
2026-06-11 19:52   ` John Hubbard
2026-06-11 22:43   ` Alexandre Courbot [this message]
2026-06-11  5:55 ` [PATCH 4/4] MAINTAINERS: add Onur Özkan " Miguel Ojeda
2026-06-11  6:36   ` Onur Özkan
2026-06-11 18:58 ` [PATCH 1/4] MAINTAINERS: add Daniel Almeida " Daniel Almeida
2026-06-11 19:07 ` Gary Guo
2026-06-12  5:03 ` 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=DJ6L0K01VI4J.1X1J16POP4JSY@nvidia.com \
    --to=acourbot@nvidia.com \
    --cc=a.hindborg@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=gary@garyguo.net \
    --cc=lossin@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tamird@kernel.org \
    --cc=tmgross@umich.edu \
    --cc=work@onurozkan.dev \
    /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.