From: Ryan Foster <foster.ryan.r@gmail.com>
To: joe@perches.com
Cc: foster.ryan.r@gmail.com, linux-kernel@vger.kernel.org,
ojeda@kernel.org, rust-for-linux@vger.kernel.org
Subject: [PATCH v2] checkpatch: warn on Rust comments with rustdoc links above items
Date: Tue, 13 Jan 2026 13:10:25 -0800 [thread overview]
Message-ID: <20260113211025.637889-1-foster.ryan.r@gmail.com> (raw)
In-Reply-To: <bfb5bee02f2e69ce1eb8c526dd4cfb82de326226.camel@perches.com>
Add a check to emit a warning when a `//` comment containing rustdoc
link patterns (like [`Foo`]) appears directly above a Rust item
declaration. This likely indicates the comment should use `///`
documentation syntax instead.
The check uses heuristics to reduce false positives:
- Only triggers on comments with rustdoc link syntax [`...`]
- Excludes doc comments (/// and //!)
- Excludes special comments (SAFETY:, TODO:, FIXME:, NOTE:, INVARIANT:,
INVARIANTS:, NB:, CAST:, GUARANTEE:, GUARANTEES:, PANIC:, OVERFLOW:,
BOUNDS:, etc.)
- Only warns when directly above a Rust item (fn, struct, enum, etc.)
Examples that trigger the warning:
// Returns a reference to the underlying [`Table`].
fn table(&self) -> &Table { }
Examples that do NOT trigger:
// SAFETY: The `ptr` is guaranteed by the C code to be valid.
unsafe fn foo() { }
// TODO: fix this later
fn bar() { }
// Regular comment without rustdoc links
fn baz() { }
v2: Apply suggestions from Joe Perches:
- Exclude /// and //! doc comments using negative lookahead
- Add more special comment tags found in tree (NB:, INVARIANTS:,
CAST:, GUARANTEES:, PANIC:, OVERFLOW:, GUARANTEE:, BOUNDS:)
Link: https://github.com/Rust-for-Linux/linux/issues/1157
Suggested-by: Miguel Ojeda <ojeda@kernel.org>
Suggested-by: Joe Perches <joe@perches.com>
Signed-off-by: Ryan Foster <foster.ryan.r@gmail.com>
---
scripts/checkpatch.pl | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 1b09b9194c94..a5a462827aba 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -3926,12 +3926,12 @@ sub process {
# Warn when a // comment that looks like documentation (contains rustdoc
# link patterns like [`Foo`]) appears directly above a Rust item.
if ($realfile =~ /\.rs$/ &&
- $rawline =~ /^\+(\s*)\/\/\s+(.*)$/) {
- my $comment_text = $2;
+ $rawline =~ m{^\+\s*//(?![/!])(.*)}s) {
+ my $comment_text = $1;
# Check if this looks like a doc comment (contains rustdoc link patterns)
# and is NOT a special comment like SAFETY:, TODO:, FIXME:, etc.
if ($comment_text =~ /\[`[^\]]+`\]/ &&
- $comment_text !~ /^\s*(?:SAFETY|TODO|FIXME|NOTE|XXX|HACK|BUG|INVARIANT):/) {
+ $comment_text !~ /^\s*(?:SAFETY|TODO|FIXME|NOTE|XXX|HACK|BUG|INVARIANTS?|NB|CAST|GUARANTEES?|PANIC|OVERFLOW|BOUNDS):/) {
# Check if next line starts a Rust item
my $nextline = $rawlines[$linenr];
if (defined($nextline) &&
--
2.52.0
next prev parent reply other threads:[~2026-01-13 21:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 20:21 [PATCH] " Ryan Foster
2026-01-13 20:57 ` Joe Perches
2026-01-13 21:10 ` Ryan Foster [this message]
2026-01-13 21:15 ` [PATCH v2] " Joe Perches
2026-01-13 21:40 ` [PATCH 1/2] " Ryan Foster
2026-01-13 22:26 ` [PATCH] " Miguel Ojeda
2026-01-13 22:38 ` 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=20260113211025.637889-1-foster.ryan.r@gmail.com \
--to=foster.ryan.r@gmail.com \
--cc=joe@perches.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
all inboxes | Powered by JetHome®