From: Andreas Hindborg <a.hindborg@kernel.org>
To: Wenzhao Liao <wenzhaoliao@ruc.edu.cn>,
axboe@kernel.dk, ojeda@kernel.org, linux-block@vger.kernel.org,
rust-for-linux@vger.kernel.org
Cc: bjorn3_gh@protonmail.com, aliceryhl@google.com,
lossin@kernel.org, boqun@kernel.org, dakr@kernel.org,
gary@garyguo.net, sunke@kylinos.cn, tmgross@umich.edu,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] rust block-mq TagSet flags plumbing and rnull blocking wiring
Date: Fri, 10 Apr 2026 14:39:30 +0200 [thread overview]
Message-ID: <87o6jrvvjx.fsf@kernel.org> (raw)
In-Reply-To: <20260410090829.1409430-1-wenzhaoliao@ruc.edu.cn>
Hi Wenzhao,
"Wenzhao Liao" <wenzhaoliao@ruc.edu.cn> writes:
> This RFC series fills a practical gap in the Rust block-mq abstraction by
> exposing blk_mq_tag_set.flags safely, then wires one in-tree consumer
> (`rnull`) via configfs as a reference.
Patches for this functionality is already submitted to list [1]. Please
take a look if those patches solve your requirement. If you require this
functionality in the kernel, please help by reviewing the patches in
that series.
Best regards,
Andreas Hindborg
[1] https://lore.kernel.org/rust-for-linux/20260216-rnull-v6-19-rc5-send-v1-12-de9a7af4b469@kernel.org/
prev parent reply other threads:[~2026-04-10 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ne6CiAojHihZEG_ev_i0nlu5Pnr_zliA5ODFH5OM1m8muKLCmOMTquymtKmTOSHR9wTVYSki1RzBYq9rhtEUhw==@protonmail.internalid>
2026-04-10 9:08 ` [RFC PATCH 0/2] rust block-mq TagSet flags plumbing and rnull blocking wiring Wenzhao Liao
2026-04-10 9:08 ` [RFC PATCH 1/2] rust: block: mq: safely expose TagSet flags Wenzhao Liao
2026-04-10 9:08 ` [RFC PATCH 2/2] block: rnull: support BLK_MQ_F_BLOCKING via configfs Wenzhao Liao
2026-04-17 12:43 ` kernel test robot
2026-04-10 12:39 ` Andreas Hindborg [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=87o6jrvvjx.fsf@kernel.org \
--to=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=axboe@kernel.dk \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-block@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=sunke@kylinos.cn \
--cc=tmgross@umich.edu \
--cc=wenzhaoliao@ruc.edu.cn \
/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.