[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e2c6bc90-9fa4-4880-adf4-212890cf0b51@kernel.org>
Date: Wed, 22 Oct 2025 11:10:02 +0200
From: Danilo Krummrich <dakr@...nel.org>
To: Boqun Feng <boqun.feng@...il.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Daniel Almeida <daniel.almeida@...labora.com>,
Matthew Maurer <mmaurer@...gle.com>, Stephen Rothwell
<sfr@...b.auug.org.au>, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>, "H. Peter Anvin" <hpa@...or.com>,
linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>,
Gary Guo <gary@...yguo.net>, lossin@...nel.org,
Andreas Hindborg <a.hindborg@...nel.org>, Alice Ryhl <aliceryhl@...gle.com>,
Trevor Gross <tmgross@...ch.edu>, rust-for-linux@...r.kernel.org
Subject: Re: [PATCH] rust: debugfs: Implement Reader for Mutex<T> only when T
is Unpin
On 10/22/25 11:07 AM, Danilo Krummrich wrote:
> On 10/22/25 5:42 AM, Boqun Feng wrote:
>> Since we are going to make `Mutex<T>` structurally pin the data (i.e.
>> `T`), therefore `.lock()` function only returns a `Guard` that can
>> dereference a mutable reference to `T` if only `T` is `Unpin`, therefore
>> restrict the impl `Reader` block of `Mutex<T>` to that.
>>
>> Signed-off-by: Boqun Feng <boqun.feng@...il.com>
>
> I assume this can go through the driver-core tree, since it's only about a
> conflict in linux-next?
Sorry, I confused this, obviously your tree is broken without this change,
please feel free to take it.
Acked-by: Danilo Krummrich <dakr@...nel.org>
Powered by blists - more mailing lists