[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <DB1SKFOR9W3I.1MBT3C6FGBWH7@kernel.org>
Date: Wed, 02 Jul 2025 20:47:25 +0200
From: "Benno Lossin" <lossin@...nel.org>
To: Onur Özkan <work@...rozkan.dev>,
<rust-for-linux@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-pm@...r.kernel.org>, <linux-kselftest@...r.kernel.org>,
<kunit-dev@...glegroups.com>
Cc: <airlied@...il.com>, <simona@...ll.ch>, <ojeda@...nel.org>,
<alex.gaynor@...il.com>, <boqun.feng@...il.com>, <gary@...yguo.net>,
<bjorn3_gh@...tonmail.com>, <a.hindborg@...nel.org>,
<aliceryhl@...gle.com>, <tmgross@...ch.edu>, <rafael@...nel.org>,
<viresh.kumar@...aro.org>, <gregkh@...uxfoundation.org>,
<maarten.lankhorst@...ux.intel.com>, <mripard@...nel.org>,
<tzimmermann@...e.de>, <davidgow@...gle.com>, <nm@...com>
Subject: Re: [PATCH v4 2/6] rust: switch to `#[expect(...)]` in init and
kunit
On Tue Jul 1, 2025 at 7:35 AM CEST, Onur Özkan wrote:
> This makes it clear that the warning is expected not just
> ignored, so we don't end up having various unnecessary
> linting rules in the codebase.
>
> Some parts of the codebase already use this approach, this
> patch just applies it more broadly.
>
> No functional changes.
>
> Signed-off-by: Onur Özkan <work@...rozkan.dev>
> ---
> rust/kernel/init.rs | 6 +++---
> rust/kernel/kunit.rs | 2 +-
> 2 files changed, 4 insertions(+), 4 deletions(-)
@Miguel are you going to pick this eventually, or do you think it should
have a new version with the right splitting?
---
Cheers,
Benno
Powered by blists - more mailing lists