From: Matthew Maurer <mmaurer@google.com>
To: Bjorn Andersson <andersson@kernel.org>
Cc: "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>,
"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: Tue, 16 Dec 2025 12:53:28 -0800 [thread overview]
Message-ID: <CAGSQo0254uMNb52aJACpuEr6O1GiUng9nNut1eecM3AFaSy_8w@mail.gmail.com> (raw)
In-Reply-To: <nddh2fawoofktjglouq5wrjubxhyqrlzftqz7lvx3xdfipncip@xgudpcfdo2bd>
On Tue, Dec 16, 2025 at 12:49 PM Bjorn Andersson <andersson@kernel.org> wrote:
>
> On Sat, Dec 13, 2025 at 12:36:00AM +0000, Matthew Maurer wrote:
> > Re-implements qcom-socinfo driver in Rust, using `Scoped`-based DebugFS
> > bindings.
>
> Okay, but why?
>
> https://docs.kernel.org/process/submitting-patches.html#describe-your-changes
>
> [..]
I'll move more of the text from the cover letter into the commit
message, but the short version is that it's intended to be a low-risk
driver to pilot vendor drivers in Android.
>
> > ---
> > base-commit: 4b31c90f86768367c84cc6e99e1deee0ec55197b
> > change-id: 20251029-qcom-socinfo-d8387c7fdb1c
> > prerequisite-change-id: 20251029-soc-bindings-9b0731bcdbed:v1
> > prerequisite-patch-id: e4da423ddabec93bd9a64004691266f9b740e0c5
> > prerequisite-patch-id: 5097ff622f8cb1d38354674cf70c1c946ac87f6c
> > prerequisite-change-id: 20251029-add-entropy-f57e12ebe110:v1
> > prerequisite-patch-id: 657de204912d2c5efff9898d3f4c51e52684d8e6
> > prerequisite-change-id: 20251212-transmute-8ab6076700a8:v1
> > prerequisite-patch-id: 4f5f7cb002d02d232083ab5c3ce6b3cb90650bd6
> > prerequisite-patch-id: 01a1f3d727e549c173dd142180741f5b6a3c866e
> > prerequisite-patch-id: ff801a7ae439876b1554b4d1132d94c825bbe74f
>
> So, it doesn't work on a clean v6.19-rc1 tree?
Correct. Those other patchsets are patchsets I'm landing which add
bindings used in this one.
>
> Regards,
> Bjorn
>
> >
> > Best regards,
> > --
> > Matthew Maurer <mmaurer@google.com>
> >
next prev parent reply other threads:[~2025-12-16 20:53 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
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 [this message]
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=CAGSQo0254uMNb52aJACpuEr6O1GiUng9nNut1eecM3AFaSy_8w@mail.gmail.com \
--to=mmaurer@google.com \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).