[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72=Dtss4xkYYZ0Abkx3=WWqPwbQsFbJA8HG-MLggXcM7aQ@mail.gmail.com>
Date: Sat, 13 Dec 2025 04:01:44 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: "Bryan O'Donoghue" <bod@...nel.org>
Cc: Matthew Maurer <mmaurer@...gle.com>, Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>,
Satya Durga Srinivasu Prabhala <satyap@...cinc.com>, Miguel Ojeda <ojeda@...nel.org>, 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>, Trilok Soni <tsoni@...cinc.com>, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, rust-for-linux@...r.kernel.org
Subject: Re: [PATCH RFC] soc: qcom: socinfo: Re-implement in Rust
On Sat, Dec 13, 2025 at 3:50 AM Bryan O'Donoghue <bod@...nel.org> wrote:
>
> One thing I notice is that, in C we alphabetise the includes.
>
> What is the normative coding standard for rust stuff I'm not sure. Is
> there any technical reason not to do the same as C includes alphabetising ?
>
> You appear to sort these kernel:: use statements earlier on in the patch.
They should be sorted, yeah (`rustfmt` takes care of that
automatically). In addition, recently we define the style for imports
(even if not all code follows it yet) -- please see:
https://docs.kernel.org/rust/coding-guidelines.html#imports
Thanks for taking a look, and I hope that clarifies.
Cheers,
Miguel
Powered by blists - more mailing lists