[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72ngUCVnYT9rQ9+ebTfTOUv7zuhJduXDO=VRRZ4myT1iqA@mail.gmail.com>
Date: Fri, 28 Mar 2025 09:19:25 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: kernel test robot <lkp@...el.com>
Cc: Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>,
oe-kbuild-all@...ts.linux.dev, Boqun Feng <boqun.feng@...il.com>,
Gary Guo <gary@...yguo.net>, Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>, Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
Danilo Krummrich <dakr@...nel.org>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org, patches@...ts.linux.dev
Subject: Re: [PATCH] rust: clarify the language unstable features in use
On Fri, Mar 28, 2025 at 1:10 AM kernel test robot <lkp@...el.com> wrote:
>
> rustfmtcheck
I will replace the newlines with an empty `//`; otherwise it reads worse.
Most of these lines will go away in some months, so I don't think it
is worth diverging from the default even if `rustfmt` had a config for
this.
Cheers,
Miguel
Powered by blists - more mailing lists