From: Danilo Krummrich <dakr@kernel.org>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: "Alex Gaynor" <alex.gaynor@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@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev
Subject: Re: [PATCH] rust: clean Rust 1.86.0 new `clippy::needless_continue` cases
Date: Wed, 2 Apr 2025 11:18:13 +0200 [thread overview]
Message-ID: <Z-0A1a3nvqFiEVtE@pollux> (raw)
In-Reply-To: <20250401221205.52381-1-ojeda@kernel.org>
On Wed, Apr 02, 2025 at 12:12:05AM +0200, Miguel Ojeda wrote:
> Starting with the upcoming Rust 1.86.0, Clippy's `needless_continue` lint
> complains about the last statement of a loop [1], including cases like:
Not related to the patch itself: Don't we need to disable new lints anyways?
Otherwise we'd get warning when compiling older kernel with newer compilers /
linters, no?
next prev parent reply other threads:[~2025-04-02 9:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 22:12 [PATCH] rust: clean Rust 1.86.0 new `clippy::needless_continue` cases Miguel Ojeda
2025-04-01 23:53 ` Benno Lossin
2025-04-02 11:13 ` Miguel Ojeda
2025-04-02 13:58 ` Tamir Duberstein
2025-04-02 15:27 ` Miguel Ojeda
2025-04-02 16:41 ` Tamir Duberstein
2025-04-02 20:29 ` Miguel Ojeda
2025-04-02 21:08 ` Tamir Duberstein
2025-04-03 17:35 ` Miguel Ojeda
2025-04-02 9:18 ` Danilo Krummrich [this message]
2025-04-02 10:55 ` 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=Z-0A1a3nvqFiEVtE@pollux \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=patches@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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).