From: Daniel Gomez <da.gomez@kernel.org>
To: Matthew Wilcox <willy@infradead.org>, 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>,
Alexandre Courbot <acourbot@nvidia.com>,
Onur Özkan <work@onurozkan.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Julia Lawall <Julia.Lawall@inria.fr>,
Corinn Tiffany <corinn.tiffany@inria.fr>,
Liam R. Howlett <liam@infradead.org>,
Philipp Stanner <pstanner@redhat.com>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
Samsung GOST <gost.dev@samsung.com>,
Daniel Gomez <da.gomez@samsung.com>
Subject: Re: [PATCH RFC v2] rust: rxarray: add rust xarray support
Date: Fri, 9 Oct 2026 21:33:25 +0200 [thread overview]
Message-ID: <20261009212431.0-da.gomez@kernel.org> (raw)
In-Reply-To: <asT5inptTPITu2j1@casper.infradead.org>
On 2026-10-06T14:37:14+01:00, Matthew Wilcox <willy@infradead.org> wrote:
> On Mon, Oct 05, 2026 at 03:37:30PM +0200, Daniel Gomez wrote:
> > From: Daniel Gomez <da.gomez@samsung.com>
> >
> > Add Rust XArray support.
> >
> > This is the Rust implementation of the XArray lib/xarray.c. As of now,
> > it supports basic functionality: store, load, load_mut and erase.
> >
> > Reviewed-by: Andreas Hindborg <a.hindborg@kernel.org>
> > Signed-off-by: Daniel Gomez <da.gomez@samsung.com>
> > ---
> > As discussed at LPC26, this is the version of the Rust XArray that is
> > ready to merge for testing and evaluating purposes following the Rust
> > reference implementation rule (experimental) [1]. Next, we will make
> > progress following the roadmap suggested in v1.
> >
> > For the motivation, see v1 link below in the changelog.
> >
> > A branch with the patches can be found here [2].
> >
> > Link: https://rust-for-linux.com/rust-reference-drivers [1]
> > Link: https://git.kernel.org/pub/scm/linux/kernel/git/da.gomez/linux.git/log/?h=rxarray-next [2]
>
> Reviewed-by: Matthew Wilcox (Oracle) <willy@infradead.org>
>
Thanks, Matthew.
Following our discussion with Miguel at LPC, I'll send PRs for the
Rust XArray to you, ie. the "PRs from their Rust sub-maintainer" option
in [1] using my tree at kernel.org [2]. If that ever doesn't fit your
schedule, the Rust for Linux tree takes them as fallback [3]. Note that
the Rust tree follows its key cycle dates, i.e. the last version of a
series should reach the list before -rc5 [4]. We have passed that date,
(for R4L tree) but I'll send the PR anyway so you can pick up when
ready.
And as I mentioned, I'm happy to take on more of the work if it helps.
[1] https://rust-for-linux.com/rust-kernel-policy#how-is-rust-introduced-in-a-subsystem
[2] https://git.kernel.org/pub/scm/linux/kernel/git/da.gomez/linux.git/log/?h=rxarray-next
[3] https://rust-for-linux.com/rust-kernel-policy#who-maintains-rust-code-in-the-kernel
[4] https://rust-for-linux.com/contributing#key-cycle-dates
prev parent reply other threads:[~2026-10-09 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 13:37 [PATCH RFC v2] rust: rxarray: add rust xarray support Daniel Gomez
2026-10-06 13:37 ` Matthew Wilcox
2026-10-09 19:33 ` Daniel Gomez [this message]
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=20261009212431.0-da.gomez@kernel.org \
--to=da.gomez@kernel.org \
--cc=Julia.Lawall@inria.fr \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=corinn.tiffany@inria.fr \
--cc=da.gomez@samsung.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=gost.dev@samsung.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=pstanner@redhat.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=willy@infradead.org \
--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.