From: Andreas Hindborg <a.hindborg@kernel.org>
To: "Alice Ryhl" <aliceryhl@google.com>
Cc: "Oliver Mangold" <oliver.mangold@pm.me>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Trevor Gross" <tmgross@umich.edu>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] rust: adding UniqueRefCounted and UniqueRef types
Date: Wed, 05 Mar 2025 16:42:04 +0100 [thread overview]
Message-ID: <87frjr8oxf.fsf@kernel.org> (raw)
In-Reply-To: <CAH5fLgjFBknTmhxQBPUdB-iNMjEkcyuLiu22-Nj-DGB1Gb7NkA@mail.gmail.com> (Alice Ryhl's message of "Wed, 05 Mar 2025 16:13:59 +0100")
"Alice Ryhl" <aliceryhl@google.com> writes:
> On Wed, Mar 5, 2025 at 3:56 PM Oliver Mangold <oliver.mangold@pm.me> wrote:
>>
[...]
>
> What is the use-case for these abstractions?
Missed this Q. It is for asserting uniqueness of a reference to a block
layer request [1].
Best regards,
Andreas Hindborg
[1] https://github.com/metaspace/linux/blob/44dd1c6eff584475f13e2a73eb4ad25df17d0d55/rust/kernel/block/mq/request.rs#L406
next prev parent reply other threads:[~2025-03-05 15:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 11:31 [PATCH v4] rust: adding UniqueRefCounted and UniqueRef types Oliver Mangold
2025-03-05 13:39 ` Alice Ryhl
2025-03-05 14:56 ` Oliver Mangold
2025-03-05 15:13 ` Alice Ryhl
2025-03-05 15:38 ` Andreas Hindborg
2025-03-05 16:02 ` Alice Ryhl
2025-03-05 17:24 ` Andreas Hindborg
2025-03-06 9:35 ` Alice Ryhl
2025-03-06 9:48 ` Andreas Hindborg
2025-03-06 10:14 ` Oliver Mangold
2025-03-06 11:31 ` Alice Ryhl
2025-03-06 12:03 ` Oliver Mangold
2025-03-06 12:08 ` Alice Ryhl
2025-03-05 15:42 ` Andreas Hindborg [this message]
2025-03-05 16:15 ` Oliver Mangold
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=87frjr8oxf.fsf@kernel.org \
--to=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=oliver.mangold@pm.me \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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