From: Boqun Feng <boqun@kernel.org>
To: Alice Ryhl <aliceryhl@google.com>
Cc: "Philipp Stanner" <phasta@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>, "Will Deacon" <will@kernel.org>,
"Waiman Long" <longman@redhat.com>, "Gary Guo" <gary@garyguo.net>,
"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>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v4] rust: sync: Accept errors for Lock payload data
Date: Sat, 31 Oct 2026 17:26:02 -0700 [thread overview]
Message-ID: <auaHGpX2jG_PNcmm@tardis.local> (raw)
In-Reply-To: <20261031191344.2913779-1-aliceryhl@google.com>
On Sat, Oct 31, 2026 at 07:13:44PM +0000, Alice Ryhl wrote:
> On Thu, Oct 22, 2026 at 06:07:26PM +0200, 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>
>
> Boqun, are you ok with merging this through drm-rust-next for JobQueue, once
> we get Gary's reviewed-by?
>
Yes ;-)
Regards,
Boqun
> Reviewed-by: Alice Ryhl <aliceryhl@google.com>
prev parent reply other threads:[~2026-11-01 0:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 16:07 [PATCH v4] rust: sync: Accept errors for Lock payload data Philipp Stanner
2026-10-31 19:13 ` Alice Ryhl
2026-11-01 0:26 ` Boqun Feng [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=auaHGpX2jG_PNcmm@tardis.local \
--to=boqun@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--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