Commit 374908a1 authored Mar 03, 2025 by Miguel Ojeda

rust: remove leftover mentions of the `alloc` crate



In commit 392e34b6 ("kbuild: rust: remove the `alloc` crate and
`GlobalAlloc`") we stopped using the upstream `alloc` crate.

Thus remove a few leftover mentions treewide.

Cc: stable@vger.kernel.org # Also to 6.12.y after the `alloc` backport lands
Fixes: 392e34b6 ("kbuild: rust: remove the `alloc` crate and `GlobalAlloc`")
Reviewed-by: Danilo Krummrich <dakr@kernel.org>
Reviewed-by: Andreas Hindborg <a.hindborg@kernel.org>
Link: https://lore.kernel.org/r/20250303171030.1081134-1-ojeda@kernel.org


Signed-off-by: Miguel Ojeda <ojeda@kernel.org>

parent 7eb17214

Documentation/rust/quick-start.rst

+1 −1

Original line number	Diff line number	Diff line
		@@ -145,7 +145,7 @@ Rust standard library source
		****************************

		The Rust standard library source is required because the build system will
		cross-compile ``core`` and ``alloc``.
		cross-compile ``core``.

		If ``rustup`` is being used, run::

rust/kernel/lib.rs

+1 −1

Original line number	Diff line number	Diff line
		@@ -6,7 +6,7 @@
		//! usage by Rust code in the kernel and is shared by all of them.
		//!
		//! In other words, all the rest of the Rust code in the kernel (e.g. kernel
		//! modules written in Rust) depends on [`core`], [`alloc`] and this crate.
		//! modules written in Rust) depends on [`core`] and this crate.
		//!
		//! If you need a kernel C API that is not ported or wrapped yet here, then
		//! do so first instead of bypassing this crate.

scripts/rustdoc_test_gen.rs

+2 −2

Original line number	Diff line number	Diff line
		@@ -15,8 +15,8 @@
		//! - Test code should be able to define functions and call them, without having to carry
		//! the context.
		//!
		//! - Later on, we may want to be able to test non-kernel code (e.g. `core`, `alloc` or
		//! third-party crates) which likely use the standard library `assert*!` macros.
		//! - Later on, we may want to be able to test non-kernel code (e.g. `core` or third-party
		//! crates) which likely use the standard library `assert*!` macros.
		//!
		//! For this reason, instead of the passed context, `kunit_get_current_test()` is used instead
		//! (i.e. `current->kunit_test`).