[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72mMEEdP1ZG2brhLWgjaQpnwG+Mcxm43B0hAvZuaq-=jBA@mail.gmail.com>
Date: Fri, 27 Jun 2025 17:55:41 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Onur Özkan <work@...rozkan.dev>
Cc: 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, airlied@...il.com, simona@...ll.ch,
ojeda@...nel.org, alex.gaynor@...il.com, boqun.feng@...il.com,
gary@...yguo.net, bjorn3_gh@...tonmail.com, lossin@...nel.org,
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 v2 0/3] replace `allow(...)` lints with `expect(...)`
On Fri, Jun 27, 2025 at 8:54 AM Onur Özkan <work@...rozkan.dev> wrote:
>
> The `#[allow(clippy::non_send_fields_in_send_ty)]` removal was tested
> on 1.81 and clippy was still happy with it. I couldn't test it on 1.78
> because when I go below 1.81 `menuconfig` no longer shows the Rust option.
> And any manual changes I make to `.config` are immediately reverted on
> `make` invocations.
For that, I recommend using the `/` command inside `menuconfig` -- it
allows you to see the dependencies of a given symbol, and whether they
are met or not. That way, it allows one to understand what else may be
missing to enable a symbol.
I hope that helps.
Cheers,
Miguel
Powered by blists - more mailing lists