From: Danilo Krummrich <dakr@kernel•org>
To: Boqun Feng <boqun.feng@gmail•com>
Cc: Peter Zijlstra <peterz@infradead•org>,
Daniel Almeida <daniel.almeida@collabora•com>,
Matthew Maurer <mmaurer@google•com>,
Stephen Rothwell <sfr@canb•auug.org.au>,
Thomas Gleixner <tglx@linutronix•de>,
Ingo Molnar <mingo@kernel•org>, "H. Peter Anvin" <hpa@zytor•com>,
linux-kernel@vger•kernel.org, linux-next@vger•kernel.org,
Miguel Ojeda <ojeda@kernel•org>,
Alex Gaynor <alex.gaynor@gmail•com>, Gary Guo <gary@garyguo•net>,
lossin@kernel•org, Andreas Hindborg <a.hindborg@kernel•org>,
Alice Ryhl <aliceryhl@google•com>,
Trevor Gross <tmgross@umich•edu>,
rust-for-linux@vger•kernel.org
Subject: Re: [PATCH] rust: debugfs: Implement Reader for Mutex<T> only when T is Unpin
Date: Wed, 22 Oct 2025 11:07:53 +0200 [thread overview]
Message-ID: <4b556c24-cd4c-4c1a-a757-5df3a6782e11@kernel.org> (raw)
In-Reply-To: <20251022034237.70431-1-boqun.feng@gmail.com>
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@gmail•com>
I assume this can go through the driver-core tree, since it's only about a
conflict in linux-next?
next prev parent reply other threads:[~2025-10-22 9:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 0:46 linux-next: build failure after merge of the tip tree Stephen Rothwell
2025-10-22 2:18 ` Boqun Feng
2025-10-22 2:51 ` Boqun Feng
2025-10-22 3:42 ` [PATCH] rust: debugfs: Implement Reader for Mutex<T> only when T is Unpin Boqun Feng
2025-10-22 9:07 ` Danilo Krummrich [this message]
2025-10-22 9:10 ` Danilo Krummrich
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=4b556c24-cd4c-4c1a-a757-5df3a6782e11@kernel.org \
--to=dakr@kernel$(echo .)org \
--cc=a.hindborg@kernel$(echo .)org \
--cc=alex.gaynor@gmail$(echo .)com \
--cc=aliceryhl@google$(echo .)com \
--cc=boqun.feng@gmail$(echo .)com \
--cc=daniel.almeida@collabora$(echo .)com \
--cc=gary@garyguo$(echo .)net \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lossin@kernel$(echo .)org \
--cc=mingo@kernel$(echo .)org \
--cc=mmaurer@google$(echo .)com \
--cc=ojeda@kernel$(echo .)org \
--cc=peterz@infradead$(echo .)org \
--cc=rust-for-linux@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
--cc=tmgross@umich$(echo .)edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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