[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72n8QvygNsdHjaMgYrXiErT82BkWm1XMkc3eUZB1Xy_uAQ@mail.gmail.com>
Date: Wed, 29 Oct 2025 19:18:39 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Uwe Kleine-König <ukleinek@...nel.org>
Cc: Michal Wilczynski <m.wilczynski@...sung.com>, Miguel Ojeda <ojeda@...nel.org>, 
	Alex Gaynor <alex.gaynor@...il.com>, Boqun Feng <boqun.feng@...il.com>, 
	Gary Guo <gary@...yguo.net>, Björn Roy Baron <bjorn3_gh@...tonmail.com>, 
	Benno Lossin <lossin@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>, 
	Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>, 
	Danilo Krummrich <dakr@...nel.org>, Drew Fustini <fustini@...nel.org>, Guo Ren <guoren@...nel.org>, 
	Fu Wei <wefu@...hat.com>, Stephen Rothwell <sfr@...b.auug.org.au>, rust-for-linux@...r.kernel.org, 
	linux-kernel@...r.kernel.org, linux-pwm@...r.kernel.org, 
	linux-riscv@...ts.infradead.org
Subject: Re: [PATCH 0/4] Introduce import_ns support for Rust
On Wed, Oct 29, 2025 at 11:04 AM Uwe Kleine-König <ukleinek@...nel.org> wrote:
>
> If you could mention the command that makes this warning visible, I'd be
> glad to add that to my repertoire of build checks.
Yeah, please do!
I do my best to keep even linux-next and stable kernels Clippy clean
as much as possible, so it would be nice to have that Clippy fix added
to -next soon.
I have other steps that maintainers/contributors should run here:
    https://rust-for-linux.com/contributing#submit-checklist-addendum
Essentially / most importantly: `rustfmt`, `rustdoc` and `CLIPPY=1`.
I am sending a couple fixes for those.
Thanks!
Cheers,
Miguel
Powered by blists - more mailing lists
 
