Description
We do not allow new unsafe
comments to enter the codebase without a // SAFETY
comment. Nowadays, we use Clippy's undocumented_unsafe_blocks
to check for that. However, some // SAFETY: TODO.
comments remain (please see the rust-next
branch). The issue is about cleaning those up.
It is not needed to fix all the comments at once (in fact, a given area/module/file should be cleaned independently), so this is a set of "good first issues". Please note that some of the comments may be easier or harder to figure out than others.
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 Suggested-by:
tag and a Link:
tag to this issue. Please see https://rust-for-linux.com/contributing for details.