init! macro produces warnings if the field names are not of standard style. Given that the warning is already generated on the struct definition side, this should be suppressed with init! macro.
I think this is caused by the reference that we added, which is a new local variable rather than just reference to other variables by name.
Reported-by: Gary Guo gary@garyguo.net
Closes: https://lore.kernel.org/rust-for-linux/DGTBJBIVFZ2K.2F1ZEFGY0G7NK@garyguo.net/
This requires submitting a proper patch to the LKML and the Rust for Linux mailing list. Please recall to test your changes (including generating the documentation if changed, running the Rust doctests if changed, etc.), to use a proper title for the commit, to sign your commit under the Developer's Certificate of Origin and to add a Reported-by: tag, a Closes: tag to this issue and a Fixes: tag to the relevant commit. Please see https://docs.kernel.org/process/submitting-patches.html and https://rust-for-linux.com/contributing for details.
init!macro produces warnings if the field names are not of standard style. Given that the warning is already generated on the struct definition side, this should be suppressed withinit!macro.I think this is caused by the reference that we added, which is a new local variable rather than just reference to other variables by name.
Reported-by: Gary Guo gary@garyguo.net
Closes: https://lore.kernel.org/rust-for-linux/DGTBJBIVFZ2K.2F1ZEFGY0G7NK@garyguo.net/
This requires submitting a proper patch to the LKML and the Rust for Linux mailing list. Please recall to test your changes (including generating the documentation if changed, running the Rust doctests if changed, etc.), to use a proper title for the commit, to sign your commit under the Developer's Certificate of Origin and to add a
Reported-by:tag, aCloses:tag to this issue and aFixes:tag to the relevant commit. Please see https://docs.kernel.org/process/submitting-patches.html and https://rust-for-linux.com/contributing for details.