From: Andreas Hindborg <a.hindborg@kernel.org>
To: "Oliver Mangold" <oliver.mangold@pm.me>
Cc: "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>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH] Rust: Implement a unique reference type URef supplementing ARef
Date: Fri, 28 Feb 2025 12:25:48 +0100 [thread overview]
Message-ID: <87r03imhtv.fsf@kernel.org> (raw)
In-Reply-To: <87wmdamiik.fsf@kernel.org> (Andreas Hindborg's message of "Fri, 28 Feb 2025 12:10:59 +0100")
Andreas Hindborg <a.hindborg@kernel.org> writes:
> Hi Oliver,
>
> "Oliver Mangold" <oliver.mangold@pm.me> writes:
>
>> For usage with block-mq, we found that having a variant of ARef which is guaranteed to be unique is useful. As chances are it is useful in general, I implemented it as kernel::types::URef. The difference between ARef and URef is basically the same as between Arc and UniqueArc.
>
> Wrap at 75 characters please :)
>
Also, be sure to Cc relevant maintainers and reviewers (I did so in this
reply). Use scripts/checkpatch.pl and refer to [1]. You can also use
`b4` [2] to get a lot of automation.
Best regards,
Andreas Hindborg
[1] https://docs.kernel.org/process/submitting-patches.html
[2] https://b4.docs.kernel.org/en/latest/contributor/prep.html
next prev parent reply other threads:[~2025-02-28 11:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jeyp4dToznpiAQYWHAABrEBIHVfxaIf7ntexop3d2AXQgnlytw3J8YFkX8E8EFKc1-USf_fVZqKhEmuNGE3O0w==@protonmail.internalid>
2025-02-21 8:04 ` [PATCH] Rust: Implement a unique reference type URef supplementing ARef Oliver Mangold
2025-02-21 8:12 ` Greg KH
2025-02-21 8:35 ` Oliver Mangold
2025-02-21 9:33 ` Andreas Hindborg
2025-02-28 11:10 ` Andreas Hindborg
2025-02-28 11:25 ` Andreas Hindborg [this message]
2025-02-28 11:31 ` Oliver Mangold
2025-02-28 12:16 ` Andreas Hindborg
2025-02-28 13:17 ` Miguel Ojeda
2025-03-04 6:19 ` kernel test robot
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=87r03imhtv.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;
as well as URLs for NNTP newsgroup(s).