Patch "rust: pin-init: internal: suppress `non_snake_case` lint in `[pin_]init!`" has been added to the 7.1-stable tree

This is a note to let you know that I've just added the patch titled

rust: pin-init: internal: suppress non_snake_case lint in [pin_]init!

to the 7.1-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
rust-pin-init-internal-suppress-non_snake_case-lint-.patch
and it can be found in the queue-7.1 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.

commit 54db70c2ed9fb176f2f097a04c55b67071dc0db7

Author: Mirko Adzic <[email protected]>
Date:   Wed May 27 18:19:54 2026 +0100

rust: pin-init: internal: suppress non_snake_case lint in [pin_]init!

[ Upstream commit 5423ef9d4db852835746001d0840231227bb0e39 ]

Allows non_snake_case lint on local variables generated in [pin_]init!.

Conceptually the identifiers in [pin_]init! just references the field names, and are not defining them, so the warning should not be generated, similar to how constructing a struct with non-snake-case field names do no generate these warnings.

Reported-by Gary Guo <[email protected]>

Closes https://github.com/Rust-for-Linux/pin-init/issues/125

Closes https://lore.kernel.org/rust-for-linux/[email protected]/ open here

Fixes 42415d163e5d ("rust: pin-init: add references to previously initialized fields")

Signed-off-by Mirko Adzic <[email protected]>

[ Reworded commit message - Gary ]

Link https://patch.msgid.link/[email protected] open here

Signed-off-by Gary Guo <[email protected]>

Signed-off-by Sasha Levin <[email protected]>

rust/pin-init/internal/src/init.rs +3 -1

index aba32825fef477..45528ab82f6a82 100644
@@ -307,7 +307,9 @@ fn init_fields(
             #init
 
             #(#cfgs)*
-            #[allow(unused_variables)]
+            // Allow `non_snake_case` since the same warning is going to be reported for the struct
+            // field.
+            #[allow(unused_variables, non_snake_case)]
             let #ident = #guard.let_binding();
         });
 

Looks like quite a lot of patches have been picked up as dependency in order to pick this to 7.1.

The warning that this fix addresses are already worked around on the user side, so it probably isn't worth backporting.