[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72k6YKjPDqcT9g5BT5pYwypH5rLjwafcEEhddTfErcnNDA@mail.gmail.com>
Date: Wed, 31 May 2023 19:14:13 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Alice Ryhl <aliceryhl@...gle.com>
Cc: rust-for-linux@...r.kernel.org, Miguel Ojeda <ojeda@...nel.org>,
Wedson Almeida Filho <wedsonaf@...il.com>,
Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Will Deacon <will@...nel.org>,
Mark Rutland <mark.rutland@....com>,
linux-kernel@...r.kernel.org, patches@...ts.linux.dev
Subject: Re: [PATCH v3 0/4] Update thread safety markers
On Wed, May 31, 2023 at 5:00 PM Alice Ryhl <aliceryhl@...gle.com> wrote:
>
> In Rust, the `Send` and `Sync` traits are used to mark in what ways a
> specific type is thread safe. In this patch series, I add some missing
> thread safety markers and improve the documentation related to them.
> This change will let you compile some code that would currently fail to
> compile even though it doesn't actually violate any thread safety rules.
>
> You can find a definition of what these marker traits mean at [1].
>
> Changes since v2:
>
> * Removed "for example" as suggested in [2].
> * Added Reviewed-by annotations from v2 review.
>
> [1]: https://stackoverflow.com/a/68708557/1704411
> [2]: https://lore.kernel.org/all/20230523165027.71600b4b.gary@garyguo.net/
Applied to `rust-next` -- thanks everyone (and Alice for taking the
effort to send this v3 even for the small change)!
Cheers,
Miguel
Powered by blists - more mailing lists