[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZC3h3q+56gM8pKOX@boqun-archlinux>
Date: Wed, 5 Apr 2023 14:02:22 -0700
From: Boqun Feng <boqun.feng@...il.com>
To: Benno Lossin <y86-dev@...tonmail.com>
Cc: Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Wedson Almeida Filho <wedsonaf@...il.com>,
Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Alice Ryhl <alice@...l.io>,
Andreas Hindborg <nmi@...aspace.dk>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
patches@...ts.linux.dev
Subject: Re: [PATCH v6 00/15] Rust pin-init API for pinned initialization of
structs
On Wed, Apr 05, 2023 at 07:35:30PM +0000, Benno Lossin wrote:
> Changelog:
> v5 -> v6:
> - Change `pinned_drop` macro to allow `mut self` in the signature.
> - Change statement fragment to tt fragemnt in `pinned_drop` to prevent
> parsing errors.
> - Move evaluation of the value in `stack_pin_init!`/`stack_try_pin_init!`
> to the beginning.
Could you elaborate why? To make sure the $val evaluation happens
unconditionally?
> - Move setting uninitialized flag in front of dropping the value in
> `StackInit::init`.
> - Remove `Unpin` requirement on `zeroed()`.
> - Add note about `Pointee` to the `Zeroable` impl on raw pointers.
>
Regards,
Boqun
Powered by blists - more mailing lists