[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72kqmMTLQaE03WEFzi2UN=Sk31TLDPi3S5UuuA5bHj3O9g@mail.gmail.com>
Date: Mon, 7 Jul 2025 15:02:31 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Benno Lossin <lossin@...nel.org>
Cc: 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, 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 Wed, Jul 2, 2025 at 8:47 PM Benno Lossin <lossin@...nel.org> wrote:
>
> @Miguel are you going to pick this eventually, or do you think it should
> have a new version with the right splitting?
I guess I could take it since the series can only introduce build
failures at worst.
However, I thought we were going to do the proper split (as
independent patches, too) and then let each maintainer pick each on
their own pace.
Cheers,
Miguel
Powered by blists - more mailing lists