From:   Martin Rodriguez Reboredo <yakoyoku@gmail.com>
To:     lina@asahilina.net
Cc:     alex.gaynor@gmail.com, asahi@lists.linux.dev,
        bjorn3_gh@protonmail.com, boqun.feng@gmail.com, gary@garyguo.net,
        linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
        masahiroy@kernel.org, nathan@kernel.org, ndesaulniers@google.com,
        nicolas@fjasle.eu, ojeda@kernel.org,
        rust-for-linux@vger.kernel.org, wedsonaf@gmail.com
Subject: Re: [PATCH] rust: Enable the new_uninit feature for kernel and driver crates
Date:   Fri, 24 Feb 2023 11:01:13 -0300
Message-Id: <20230224140113.745953-1-yakoyoku@gmail.com>
In-Reply-To: <20230224-rust-new_uninit-v1-1-c951443d9e26@asahilina.net>
References: <20230224-rust-new_uninit-v1-1-c951443d9e26@asahilina.net>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Fri, Feb 24, 2023 at 05:09:47PM +0900, Asahi Lina wrote:=0D
> The unstable new_uninit feature enables various library APIs to create=0D
> uninitialized containers, such as `Box::assume_init()`. This is=0D
> necessary to build abstractions that directly initialize memory at the=0D
> target location, instead of doing copies through the stack.=0D
> =0D
> Will be used by the DRM scheduler abstraction in the kernel crate, and=0D
> by field-wise initialization (e.g. using `place!()` or a future=0D
> replacement macro which may itself live in `kernel`) in driver crates.=0D
=0D
Very useful to me as some constructors in the USB bindings that I'm=0D
writting might make use of unitialized memory.=0D
=0D
Reviewed-by: Martin Rodriguez Reboredo <yakoyoku@gmail.com>=0D