From: Joe Perches <joe@perches.com>
To: Ryan Foster <foster.ryan.r@gmail.com>
Cc: linux-kernel@vger.kernel.org, ojeda@kernel.org,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v2] checkpatch: warn on Rust comments with rustdoc links above items
Date: Tue, 13 Jan 2026 13:15:03 -0800 [thread overview]
Message-ID: <841bb4c27f174fb4f11aaf7bb5f070b96835b4b9.camel@perches.com> (raw)
In-Reply-To: <20260113211025.637889-1-foster.ryan.r@gmail.com>
On Tue, 2026-01-13 at 13:10 -0800, Ryan Foster wrote:
> 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.
You sent a delta patch from v1 as v2.
Please send the entire patch instead.
next prev parent reply other threads:[~2026-01-13 21:15 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 ` [PATCH v2] " Ryan Foster
2026-01-13 21:15 ` Joe Perches [this message]
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=841bb4c27f174fb4f11aaf7bb5f070b96835b4b9.camel@perches.com \
--to=joe@perches.com \
--cc=foster.ryan.r@gmail.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®