[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72ma7p9q8Usos6=Opv+YwzOXKgLXj6EEBUsfY2OY7KniGg@mail.gmail.com>
Date: Mon, 10 Apr 2023 04:54:02 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Asahi Lina <lina@...hilina.net>
Cc: Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Wedson Almeida Filho <wedsonaf@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Masahiro Yamada <masahiroy@...nel.org>,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Nicolas Schier <nicolas@...sle.eu>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-kbuild@...r.kernel.org, asahi@...ts.linux.dev
Subject: Re: [PATCH] rust: Enable the new_uninit feature for kernel and driver crates
On Fri, Feb 24, 2023 at 9:10 AM Asahi Lina <lina@...hilina.net> wrote:
>
> The unstable new_uninit feature enables various library APIs to create
> uninitialized containers, such as `Box::assume_init()`. This is
> necessary to build abstractions that directly initialize memory at the
> target location, instead of doing copies through the stack.
>
> Will be used by the DRM scheduler abstraction in the kernel crate, and
> by field-wise initialization (e.g. using `place!()` or a future
> replacement macro which may itself live in `kernel`) in driver crates.
>
> See [1] [2] [3] for background information.
>
> [1] https://github.com/Rust-for-Linux/linux/issues/879
> [2] https://github.com/Rust-for-Linux/linux/issues/2
> [3] https://github.com/rust-lang/rust/issues/63291
Applied to `rust-next` (reworded to use `Link` tags). Thanks!
Cheers,
Miguel
Powered by blists - more mailing lists