From: Philipp Stanner <phasta@mailbox.org>
To: "Gary Guo" <gary@garyguo.net>,
"Philipp Stanner" <phasta@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>, "Will Deacon" <will@kernel.org>,
"Boqun Feng" <boqun@kernel.org>,
"Waiman Long" <longman@redhat.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Lyude Paul" <lyude@redhat.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Onur Özkan" <work@onurozkan.dev>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Tamir Duberstein" <tamird@kernel.org>,
"Alexandre Courbot" <acourbot@nvidia.com>
Cc: linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH] rust: sync: Accept errors for Lock payload data
Date: Mon, 28 Sep 2026 10:10:26 +0200 [thread overview]
Message-ID: <dc8b56abedca3c6d17649de7f682e4af0b91b645.camel@mailbox.org> (raw)
In-Reply-To: <DLNHF9TPLXK2.1VQ2LJ0U6Y07K@garyguo.net>
On Thu, 2026-09-24 at 11:41 +0100, Gary Guo wrote:
> On Thu Sep 24, 2026 at 9:55 AM BST, Philipp Stanner wrote:
> > The `Lock` baseclass currently does not allow for fallible user-data.
> > This can cause conflicts when used with other primitives, for example
> > when a lock shall be pin-initialized with payload data that is fallible.
> >
> > Add support for the lock base class so that it works with
> > try_pin_init!(). Adjust spinlock and mutex accordingly.
> >
> > Signed-off-by: Philipp Stanner <phasta@kernel.org>
> > ---
> > Regarding removal of the CStrExt, I got "unused import" errors because
> > of it. Don't fully understand why?
>
> Because it's part of the prelude.
But why was it imported `as _` ?
P.
next prev parent reply other threads:[~2026-09-28 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 8:55 Philipp Stanner
2026-09-24 10:41 ` Gary Guo
2026-09-28 8:10 ` Philipp Stanner [this message]
2026-09-28 8:45 ` Miguel Ojeda
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=dc8b56abedca3c6d17649de7f682e4af0b91b645.camel@mailbox.org \
--to=phasta@mailbox.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=lossin@kernel.org \
--cc=lyude@redhat.com \
--cc=mingo@redhat.com \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=phasta@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=will@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®