[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAH5fLgiTTXVMs3tzrHAU1rwQDCs_VPuPgEVcEkjbu+rNT=35vA@mail.gmail.com>
Date: Tue, 1 Jul 2025 13:27:17 +0200
From: Alice Ryhl <aliceryhl@...gle.com>
To: Marcelo Moreira <marcelomoreira1905@...il.com>, Danilo Krummrich <dakr@...nel.org>
Cc: 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 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?
Alice
Powered by blists - more mailing lists