[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aGPJFw_Ouj8MNbuq@pollux>
Date: Tue, 1 Jul 2025 13:40:07 +0200
From: Danilo Krummrich <dakr@...nel.org>
To: Alice Ryhl <aliceryhl@...gle.com>
Cc: Marcelo Moreira <marcelomoreira1905@...il.com>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
lossin@...nel.org, ojeda@...nel.org, skhan@...uxfoundation.org,
linux-kernel-mentees@...ts.linuxfoundation.org,
~lkcamp/patches@...ts.sr.ht
Subject: Re: [PATCH v5 0/2] rust: revocable: documentation and refactorings
On Tue, Jul 01, 2025 at 01:27:17PM +0200, Alice Ryhl wrote:
> On Thu, Jun 26, 2025 at 6:59 PM Marcelo Moreira
> <marcelomoreira1905@...il.com> wrote:
> >
> > This patch series brings documentation and refactorings to the `Revocable` type.
> >
> > Changes include:
> > - Clarifying the write invariant and updating associated safety comments for `Revocable<T>`.
> > - Splitting the internal `revoke_internal` function into two distinct, explicit functions: `revoke()` (safe, synchronizing with RCU) and `revoke_nosync()` (unsafe, without RCU synchronization), now returning `bool` to indicate revocation status.
> >
> > Marcelo Moreira (2):
> > rust: revocable: Refactor revocation mechanism to remove generic
> > revoke_internal
> > rust: revocable: Clarify write invariant and update safety comments
>
> Danilo, did you have Revocable / Devres changes that conflict with this?
Yes, but I sent them to Linus for -rc3 already. Given that rust-next is based on
-rc3, we should be good. There shouldn't be any further conflicts.
Powered by blists - more mailing lists