From: yilin <1479826151@qq.com>
To: Miguel Ojeda <ojeda@kernel.org>, rust-for-linux@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, yilin <1479826151@qq.com>
Subject: [PATCH 0/3] rust: documentation fixes and API consistency improvements
Date: Thu, 11 Dec 2025 23:15:53 +0800 [thread overview]
Message-ID: <tencent_08D4DAD1AE568FC79EB11A8109D8926A2309@qq.com> (raw)
This patch series fixes documentation issues and improves API naming
consistency in the Rust for Linux codebase:
- Patch 1/3 fixes an incorrect type in device_id safety documentation
- Patch 2/3 removes redundant safety documentation in the dma module
- Patch 3/3 renames cpumask methods to follow the constructor pattern
yilin (3):
rust: device_id: replace possible incorrect word in safety document
rust: dma: remove incorrect safety documentation
rust: cpumask: rename methods of Cpumask for clarity and consistency
rust/kernel/cpumask.rs | 10 +++++-----
rust/kernel/device_id.rs | 2 +-
rust/kernel/dma.rs | 2 --
3 files changed, 6 insertions(+), 8 deletions(-)
--
2.34.1
reply other threads:[~2025-12-11 15:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tencent_08D4DAD1AE568FC79EB11A8109D8926A2309@qq.com \
--to=1479826151@qq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).