Changes in macros

211dcf77 - rust: clean Rust 1.88.0's `clippy::uninlined_format_args` lint

Fri, 02 May 2025 14:00:00 +0000

rust: clean Rust 1.88.0's `clippy::uninlined_format_args` lintStarting with Rust 1.88.0 (expected 2025-06-26) [1], `rustc` may moveback the `uninlined_format_args` to `style` from `pedantic` (it wasthere waiting for rust-analyzer suppotr), and thus we will start to seelints like: warning: variables can be used directly in the `format!` string --> rust/macros/kunit.rs:105:37 | 105 | let kunit_wrapper_fn_name = format!("kunit_rust_wrapper_{}", test); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#uninlined_format_args help: change this to | 105 - let kunit_wrapper_fn_name = format!("kunit_rust_wrapper_{}", test); 105 + let kunit_wrapper_fn_name = format!("kunit_rust_wrapper_{test}");There is even a case that is a pure removal: warning: variables can be used directly in the `format!` string --> rust/macros/module.rs:51:13 | 51 | format!("{field}={content}\0", field = field, content = content) | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#uninlined_format_args help: change this to | 51 - format!("{field}={content}\0", field = field, content = content) 51 + format!("{field}={content}\0")The lints all seem like nice cleanups, thus just apply them.We may want to disable `allow-mixed-uninlined-format-args` in the future.Cc: stable@vger.kernel.org # Needed in 6.12.y and later (Rust is pinned in older LTSs).Link: https://github.com/rust-lang/rust-clippy/pull/14160 [1]Acked-by: Benno Lossin Reviewed-by: Tamir Duberstein Reviewed-by: Alice Ryhl Link: https://lore.kernel.org/r/20250502140237.1659624-6-ojeda@kernel.orgSigned-off-by: Miguel Ojeda List of files: /linux-6.15/rust/macros/kunit.rs/linux-6.15/rust/macros/module.rs

c0010452 - rust: macros: add macro to easily run KUnit tests

Fri, 07 Mar 2025 09:00:00 +0000

rust: macros: add macro to easily run KUnit testsAdd a new procedural macro (`#[kunit_tests(kunit_test_suit_name)]`) torun KUnit tests using a user-space like syntax.The macro, that should be used on modules, transforms every `#[test]`in a `kunit_case!` and adds a `kunit_unsafe_test_suite!` registeringall of them.The only difference with user-space tests is that instead of using`#[cfg(test)]`, `#[kunit_tests(kunit_test_suit_name)]` is used.Note that `#[cfg(CONFIG_KUNIT)]` is added so the test module is notcompiled when `CONFIG_KUNIT` is set to `n`.Reviewed-by: David Gow Signed-off-by: José Expósito Co-developed-by: Boqun Feng Signed-off-by: Boqun Feng Co-developed-by: Miguel Ojeda Signed-off-by: Miguel Ojeda Reviewed-by: Tamir Duberstein Signed-off-by: David Gow Link: https://lore.kernel.org/r/20250307090103.918788-3-davidgow@google.com[ Removed spurious (in rendered form) newline in docs. - Miguel ]Signed-off-by: Miguel Ojeda List of files: /linux-6.15/rust/macros/lib.rs

dbd5058b - rust: make pin-init its own crate

Sat, 08 Mar 2025 11:00:00 +0000

rust: make pin-init its own crateRename relative paths inside of the crate to still refer to the sameitems, also rename paths inside of the kernel crate and adjust the buildsystem to build the crate.[ Remove the `expect` (and thus the `lint_reasons` feature) since the tree now uses `quote!` from `rust/macros/export.rs`. Remove the `TokenStream` import removal, since it is now used as well. In addition, temporarily (i.e. just for this commit) use an `--extern force:alloc` to prevent an unknown `new_uninit` error in the `rustdoc` target. For context, please see a similar case in: https://lore.kernel.org/lkml/20240422090644.525520-1-ojeda@kernel.org/ And adjusted the message above. - Miguel ]Signed-off-by: Benno Lossin Reviewed-by: Fiona Behrens Tested-by: Andreas Hindborg Link: https://lore.kernel.org/r/20250308110339.2997091-16-benno.lossin@proton.meSigned-off-by: Miguel Ojeda List of files: /linux-6.15/rust/macros/helpers.rs