From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sidong Yang <sidong.yang@furiosa.ai>
Cc: Jens Axboe <axboe@kernel.dk>,
Daniel Almeida <daniel.almeida@collabora.com>,
Caleb Sander Mateos <csander@purestorage.com>,
Benno Lossin <lossin@kernel.org>, Miguel Ojeda <ojeda@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
io-uring@vger.kernel.org
Subject: Re: [PATCH v5 0/4] Rust io_uring command abstraction for miscdevice
Date: Sun, 26 Apr 2026 23:30:22 +0200 [thread overview]
Message-ID: <2026042602-harness-chest-bfcf@gregkh> (raw)
In-Reply-To: <20260415090851.4897-1-sidong.yang@furiosa.ai>
On Wed, Apr 15, 2026 at 09:02:11AM +0000, Sidong Yang wrote:
> This series introduces Rust abstractions for io_uring commands
> (`IORING_OP_URING_CMD`) and wires them up to the miscdevice framework,
> allowing Rust drivers to handle io_uring passthrough commands.
>
> The series is structured as follows:
>
> 1. Add io_uring C headers to Rust bindings.
> 2. Core io_uring Rust abstractions (IoUringCmd, QueuedIoUringCmd,
> IoUringSqe, UringCmdAction type-state pattern, IoUringTaskWork trait).
> 3. MiscDevice trait extension with uring_cmd callback.
> 4. Sample demonstrating async uring_cmd handling via workqueue.
Again, I can't take this until we have a "real" user. Please wait to
submit it at that point in time.
thanks,
greg k-h
prev parent reply other threads:[~2026-04-27 3:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 9:02 [PATCH v5 0/4] Rust io_uring command abstraction for miscdevice Sidong Yang
2026-04-15 9:02 ` [PATCH v5 1/4] rust: bindings: add io_uring headers in bindings_helper.h Sidong Yang
2026-04-15 9:02 ` [PATCH v5 2/4] rust: io_uring: introduce rust abstraction for io-uring cmd Sidong Yang
2026-04-15 9:02 ` [PATCH v5 3/4] rust: miscdevice: Add `uring_cmd` support Sidong Yang
2026-04-15 9:02 ` [PATCH v5 4/4] samples: rust: Add `uring_cmd` example to `rust_misc_device` Sidong Yang
2026-04-26 21:30 ` Greg Kroah-Hartman [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=2026042602-harness-chest-bfcf@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=daniel.almeida@collabora.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sidong.yang@furiosa.ai \
/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.