From: Sylvan Smit <sylvan@sylvansmit.com>
To: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Sylvan Smit <sylvan@sylvansmit.com>, Miguel Ojeda <ojeda@kernel.org>
Subject: [PATCH] rust: list: Fix typo `much` in arc.rs
Date: Thu, 29 May 2025 18:29:23 +0200 [thread overview]
Message-ID: <20250529162923.434978-1-sylvan@sylvansmit.com> (raw)
Correct the typo (s/much/must) in the ListArc documentation.
Suggested-by: Miguel Ojeda <ojeda@kernel.org>
Fixes: a48026315cd7 ("rust: list: add tracking for ListArc")
Closes: https://github.com/Rust-for-Linux/linux/issues/1166
Signed-off-by: Sylvan Smit <sylvan@sylvansmit.com>
---
rust/kernel/list/arc.rs | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/rust/kernel/list/arc.rs b/rust/kernel/list/arc.rs
index 8401ddcd178a..d92bcf665c89 100644
--- a/rust/kernel/list/arc.rs
+++ b/rust/kernel/list/arc.rs
@@ -74,7 +74,7 @@ pub unsafe trait TryNewListArc<const ID: u64 = 0>: ListArcSafe<ID> {
///
/// * The `untracked` strategy does not actually keep track of whether a [`ListArc`] exists. When
/// using this strategy, the only way to create a [`ListArc`] is using a [`UniqueArc`].
-/// * The `tracked_by` strategy defers the tracking to a field of the struct. The user much specify
+/// * The `tracked_by` strategy defers the tracking to a field of the struct. The user must specify
/// which field to defer the tracking to. The field must implement [`ListArcSafe`]. If the field
/// implements [`TryNewListArc`], then the type will also implement [`TryNewListArc`].
///
--
2.49.0
next reply other threads:[~2025-05-29 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 16:29 Sylvan Smit [this message]
2025-05-29 16:32 ` [PATCH] rust: list: Fix typo `much` in arc.rs Benno Lossin
2025-05-29 21:39 ` Miguel Ojeda
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=20250529162923.434978-1-sylvan@sylvansmit.com \
--to=sylvan@sylvansmit.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