From: Andreas Hindborg <a.hindborg@kernel.org>
To: "Bart Van Assche" <bvanassche@acm.org>,
"Bean Huo" <beanhuo@iokpp.de>,
jaemyung.lee@samsung.com, "Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@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>
Cc: linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH RFC] drivers/rufs: add Rust UFS host controller driver
Date: Wed, 16 Sep 2026 19:46:59 +0200 [thread overview]
Message-ID: <87a4ph3x7w.fsf@t14s.mail-host-address-is-not-set> (raw)
In-Reply-To: <d19d0b37-a599-426c-b54f-cf9b16462904@acm.org>
Bart Van Assche <bvanassche@acm.org> writes:
> On 9/13/26 6:10 AM, Andreas Hindborg wrote:
>> I understand that userland tools need to be updated, and that
>> carries cost.
> Hmm ... my understanding is that the Rust UFS host driver needs to be
> modified. Why should user space code have to know what UFS driver has
> been activated in the kernel? sysfs ABIs are assumed to be stable, isn't
> it?
There is a choice to be made. Arguments could be made in both
directions. One could argue that this is a new driver, so technically it
is a new ABI and as such there, is no stability requirement.
With a goal of constructing a more simple driver, sticking with scsi
legacy user space interfaces might not make sense.
Best regards,
Andreas Hindborg
next prev parent reply other threads:[~2026-09-16 17:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 15:52 Jaemyung Lee via B4 Relay
2026-09-11 16:18 ` Andreas Hindborg
2026-09-11 19:03 ` Bart Van Assche
2026-09-12 11:33 ` Andreas Hindborg
2026-09-11 20:27 ` Greg KH
2026-09-12 11:00 ` Andreas Hindborg
2026-09-12 12:10 ` James Bottomley
2026-09-12 12:48 ` Andreas Hindborg
2026-09-12 13:37 ` Bart Van Assche
2026-09-12 13:55 ` James Bottomley
2026-09-12 15:45 ` Andreas Hindborg
2026-09-13 0:30 ` Bart Van Assche
2026-09-14 20:27 ` Bart Van Assche
2026-09-16 16:15 ` Jaemyung Lee
2026-09-14 10:02 ` Johannes Thumshirn
2026-09-13 12:23 ` Bean Huo
2026-09-13 13:44 ` Andreas Hindborg
2026-09-16 16:28 ` Jaemyung Lee
2026-09-11 21:44 ` Bean Huo
2026-09-12 11:20 ` Andreas Hindborg
2026-09-13 12:09 ` Bean Huo
2026-09-13 13:10 ` Andreas Hindborg
2026-09-16 16:21 ` Bart Van Assche
2026-09-16 17:46 ` Andreas Hindborg [this message]
2026-09-16 16:46 ` Jaemyung Lee
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=87a4ph3x7w.fsf@t14s.mail-host-address-is-not-set \
--to=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=beanhuo@iokpp.de \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=bvanassche@acm.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=jaemyung.lee@samsung.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®