From: Joe Perches <joe@perches.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Patrick Miller <paddymills@proton.me>
Cc: "Andy Whitcroft" <apw@canonical.com>,
"Dwaipayan Ray" <dwaipayanray1@gmail.com>,
"Lukas Bulwahn" <lukas.bulwahn@gmail.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@samsung.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
"Hridesh MG" <hridesh699@gmail.com>
Subject: Re: [PATCH v5 2/2] checkpatch: warn on known non-plural rust doc headers and empty doc comments
Date: Wed, 02 Oct 2024 05:28:04 -0700 [thread overview]
Message-ID: <9a8ed16ffc65d587ed2ff2d1e95bd61fdca5cc90.camel@perches.com> (raw)
In-Reply-To: <CANiq72kEPEcqqJmLEtT7=Ku5mseHe6Js_jptVQHMzRwfUzFtMQ@mail.gmail.com>
On Wed, 2024-10-02 at 13:56 +0200, Miguel Ojeda wrote:
> We already have other checks for Rust files that are shared with other
> languages. Perhaps we can be slightly more clear with "checks for Rust
> files (only)" or "Rust-only checks" or "checks that only apply to Rust
> files"?
I'll get this sorted in the next week or so
and forwarded on.
next prev parent reply other threads:[~2024-10-02 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 2:28 [PATCH v5 1/2] docs: rust: make section names plural Patrick Miller
2024-10-02 2:29 ` [PATCH v5 2/2] checkpatch: warn on known non-plural rust doc headers and empty doc comments Patrick Miller
2024-10-02 11:56 ` Miguel Ojeda
2024-10-02 12:28 ` Joe Perches [this message]
2024-10-02 12:31 ` Hridesh Mg
2024-10-02 12:46 ` Miguel Ojeda
2025-05-26 18:44 ` [PATCH v5 1/2] docs: rust: make section names plural 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=9a8ed16ffc65d587ed2ff2d1e95bd61fdca5cc90.camel@perches.com \
--to=joe@perches.com \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=apw@canonical.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dwaipayanray1@gmail.com \
--cc=gary@garyguo.net \
--cc=hridesh699@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=paddymills@proton.me \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=wedsonaf@gmail.com \
/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).