From: Bart Van Assche <bvanassche@acm.org>
To: Andreas Hindborg <a.hindborg@kernel.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Greg KH <gregkh@linuxfoundation.org>,
jaemyung.lee@samsung.com
Cc: "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>,
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, "Jens Axboe" <axboe@kernel.dk>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"Bean Huo" <beanhuo@iokpp.de>
Subject: Re: [PATCH RFC] drivers/rufs: add Rust UFS host controller driver
Date: Mon, 14 Sep 2026 13:27:23 -0700 [thread overview]
Message-ID: <3c1c0025-2a88-463d-8aeb-6331dd09bad3@acm.org> (raw)
In-Reply-To: <ba386a0a-8022-4c3f-a1c1-bb22205b51d4@acm.org>
On 9/12/26 5:30 PM, Bart Van Assche wrote:
> On 9/12/26 8:45 AM, Andreas Hindborg wrote:
>> If we expected this new driver to be a strict subset of ufshcd, we would
>> not build it. The reason to do it is the features that do not fit the
>> scsi midlayer.
>
> That's a super vague statement. What features do you want to implement
> that do not fit the SCSI mid-layer? If this is about implementing non-
> standard SCSI commands, REQ_OP_DRV_IN and REQ_OP_DRV_OUT should be
> sufficient, isn't it? Please note that this is not an endorsement for
> implementing non-standard commands in UFS devices. Non-standard storage
> commands complicate filesystem development and maintenance, especially
> if which commands are supported depends on both the manufacturer of the
> storage device and the device model.
(replying to my own e-mail)
Since my question has not been answered, I assume that REQ_OP_DRV_IN and
REQ_OP_DRV_OUT are sufficient. If REQ_OP_DRV_IN and REQ_OP_DRV_OUT are
sufficient, there is no longer a reason to implement a new UFS driver
subsystem because the upstream UFS driver already supports these
operations, isn't it?
Bart.
next prev parent reply other threads:[~2026-09-14 20:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 15:52 [PATCH RFC] drivers/rufs: add Rust UFS host controller driver Jaemyung Lee
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 [this message]
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
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=3c1c0025-2a88-463d-8aeb-6331dd09bad3@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=axboe@kernel.dk \
--cc=beanhuo@iokpp.de \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--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=martin.petersen@oracle.com \
--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.