From: Keith Busch <kbusch@kernel.org>
To: Andreas Hindborg <a.hindborg@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>,
lsf-pc@lists.linux-foundation.org, linux-block@vger.kernel.org,
Bart Van Assche <bvanassche@acm.org>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>,
Damien Le Moal <dlemoal@kernel.org>,
Daniel Gomez <da.gomez@samsung.com>,
Hannes Reinecke <hare@suse.de>,
Hans Holmberg <Hans.Holmberg@wdc.com>, Jan Kara <jack@suse.cz>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
John Pittman <jpittman@redhat.com>,
John Stultz <jstultz@google.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Miguel Ojeda <ojeda@kernel.org>, Ming Lei <ming.lei@redhat.com>,
Niklas Cassel <cassel@kernel.org>,
Nitesh Shetty <nj.shetty@samsung.com>,
Oliver Mangold <oliver.mangold@pm.me>,
Pankaj Raghav <kernel@pankajraghav.com>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Theodore Tso <tytso@mit.edu>,
Wedson Almeida Filho <wedsonaf@gmail.com>,
gost.dev@samsung.com, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [LSF/MM/BPF TOPIC][RESEND] Status of Rust in the block subsystem
Date: Mon, 16 Mar 2026 17:51:45 -0600 [thread overview]
Message-ID: <abiXkTSpZ8CWbJVx@kbusch-mbp> (raw)
In-Reply-To: <87ikb2mrib.fsf@t14s.mail-host-address-is-not-set>
On Wed, Mar 11, 2026 at 02:21:00PM +0100, Andreas Hindborg wrote:
> As this topic was not selected for discussion at LSF, and I did not
> receive an invitation for LSF this year, I propose that we discuss these
> two topics on list.
>
> I do believe that these topics need to be discussed, and I would very
> much appreciate your input.
I can sympathise the difficulty of maintaining external modules.
In terms of this being a reference driver, that implies some future
hardware driver may leverage this for its development. Is there anything
in mind at this point for production? If so, maybe that use case should
take the lead. But either way, I think rust-nvme upstream inclusion
would invite confusion. Once it's upstream, it's no longer a reference
when distros and users turn it on.
next prev parent reply other threads:[~2026-03-16 23:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 21:31 [LSF/MM/BPF TOPIC][RESEND] Status of Rust in the block subsystem Andreas Hindborg
2026-03-11 13:21 ` Andreas Hindborg
2026-03-16 23:51 ` Keith Busch [this message]
2026-03-17 7:18 ` Hannes Reinecke
2026-03-17 7:36 ` Miguel Ojeda
2026-03-17 8:07 ` Andreas Hindborg
2026-03-17 8:18 ` Greg KH
2026-03-17 8:30 ` Andreas Hindborg
2026-03-17 8:51 ` Greg KH
2026-03-17 9:36 ` Andreas Hindborg
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=abiXkTSpZ8CWbJVx@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=Hans.Holmberg@wdc.com \
--cc=a.hindborg@kernel.org \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=cassel@kernel.org \
--cc=chaitanyak@nvidia.com \
--cc=da.gomez@samsung.com \
--cc=dlemoal@kernel.org \
--cc=gost.dev@samsung.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=johannes.thumshirn@wdc.com \
--cc=jpittman@redhat.com \
--cc=jstultz@google.com \
--cc=kernel@pankajraghav.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=nj.shetty@samsung.com \
--cc=ojeda@kernel.org \
--cc=oliver.mangold@pm.me \
--cc=rust-for-linux@vger.kernel.org \
--cc=sagi@grimberg.me \
--cc=shinichiro.kawasaki@wdc.com \
--cc=tytso@mit.edu \
--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