All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bod@kernel.org>
To: "Matthew Maurer" <mmaurer@google.com>,
	"Bjorn Andersson" <andersson@kernel.org>,
	"Konrad Dybcio" <konradybcio@kernel.org>,
	"Satya Durga Srinivasu Prabhala" <satyap@quicinc.com>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>
Cc: Trilok Soni <tsoni@quicinc.com>,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	rust-for-linux@vger.kernel.org
Subject: Re: [PATCH RFC] soc: qcom: socinfo: Re-implement in Rust
Date: Sat, 13 Dec 2025 02:50:14 +0000	[thread overview]
Message-ID: <5fbecf9c-b8bc-4027-ae30-d7c49212bc56@kernel.org> (raw)
In-Reply-To: <20251213-qcom-socinfo-v1-1-5daa7f5f2a85@google.com>

On 13/12/2025 00:36, Matthew Maurer wrote:

> +//! Re-implementation of Qualcomm's Socinfo driver in Rust
> +use core::fmt;
> +use core::fmt::Formatter;
> +use kernel::debugfs::{Scope, ScopedDir};
> +use kernel::device::Core;
> +use kernel::module_platform_driver;
> +use kernel::platform::{self, Device};
> +use kernel::prelude::{fmt, pin_data, Error, PinInit, Result};
> +use kernel::soc;
> +use kernel::str::{CStr, CStrExt, CString};
> +use kernel::transmute::FromBytes;
> +use kernel::{c_str, pr_warn, try_pin_init};
> +use pin_init::pin_init_scope;

Probably learning more from your patch than being in a position to 
review - thanks for that.

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.

---
bod

  reply	other threads:[~2025-12-13  2:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <x2HszWYqUaRfzLW8I1wOegJRSBRXVUzqafU9O_QLG1E-OjqkyUPQKn-jM9dzhvsgMW_M0NGXvrgEkN0p9mV7ww==@protonmail.internalid>
2025-12-13  0:36 ` [PATCH RFC] soc: qcom: socinfo: Re-implement in Rust Matthew Maurer
2025-12-13  2:50   ` Bryan O'Donoghue [this message]
2025-12-13  3:01     ` Miguel Ojeda
2025-12-13  3:54   ` Dmitry Baryshkov
2025-12-13 16:58     ` Matthew Maurer
2025-12-15 12:11       ` Gary Guo
2025-12-15 19:44       ` Dmitry Baryshkov
2025-12-16  0:55         ` Matthew Maurer
2025-12-16  9:45           ` Danilo Krummrich
2025-12-13 13:27   ` Greg KH
2025-12-13 16:26     ` Matthew Maurer
2025-12-13 17:11       ` Matthew Maurer
2025-12-13 13:57   ` Greg KH
2025-12-13 16:24     ` Matthew Maurer
2025-12-13 17:08       ` Matthew Maurer
2025-12-16 21:00       ` Bjorn Andersson
2025-12-16 20:55         ` Matthew Maurer
2025-12-16 22:14           ` Bjorn Andersson
2025-12-16 22:32             ` Matthew Maurer
2025-12-16 20:57   ` Bjorn Andersson
2025-12-16 20:53     ` Matthew Maurer
2025-12-16 22:01       ` Bjorn Andersson
2025-12-16 22:13         ` Matthew Maurer
2025-12-16 23:13           ` Bjorn Andersson
2025-12-16 23:32             ` Matthew Maurer
2025-12-17  0:23               ` Bjorn Andersson
2025-12-17  0:27                 ` Matthew Maurer
2025-12-17 18:35             ` Danilo Krummrich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5fbecf9c-b8bc-4027-ae30-d7c49212bc56@kernel.org \
    --to=bod@kernel.org \
    --cc=a.hindborg@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=andersson@kernel.org \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=gary@garyguo.net \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=mmaurer@google.com \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=satyap@quicinc.com \
    --cc=tmgross@umich.edu \
    --cc=tsoni@quicinc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.