Skip to content

Use safety sections in cpufreq documentation #1169

Closed

Description

@ojeda

There are some /// SAFETY lines in the docs of cpufreq that should have been sections instead.


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.

Activity

  1. added
    • docsRelated to `Documentation/rust/`, `samples/`, generated docs, doctests, typos...
    easyExpected to be an easy issue to resolve.
    on Jun 9, 2025
  2. safstromo commented on Jun 10, 2025

    @safstromo

    Hello!
    I would like to give this a go as a first issue 😃

  3. added 3 commits that reference this issue on Jun 10, 2025
    8d7cc8b
    6ea81a7
    e8a5198
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    easyExpected to be an easy issue to resolve.good first issueGood for newcomers• docsRelated to `Documentation/rust/`, `samples/`, generated docs, doctests, typos...

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions