From: "Danilo Krummrich" <dakr@kernel.org>
To: "Matthew Maurer" <mmaurer@google.com>
Cc: "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>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
"Lee Jones" <lee@kernel.org>
Subject: Re: [PATCH v4 2/3] docs: ABI: sysfs-devices-soc: Fix swapped sample values
Date: Mon, 29 Dec 2025 15:07:18 +0100 [thread overview]
Message-ID: <DFARC0ZSLQUS.30H5E9NMYJGJ9@kernel.org> (raw)
In-Reply-To: <20251226-soc-bindings-v4-2-2c2fac08f820@google.com>
On Fri Dec 26, 2025 at 9:17 PM CET, Matthew Maurer wrote:
> The sample values for `family` and `machine` were swapped relative to
> what the driver actually does, and doesn't match the field description.
>
> Reviewed-by: Lee Jones <lee@kernel.org>
> Signed-off-by: Matthew Maurer <mmaurer@google.com>
Applied to driver-core-linus, thanks!
next prev parent reply other threads:[~2025-12-29 14:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-26 20:17 [PATCH v4 0/3] Support exporting SoC info from Rust Matthew Maurer
2025-12-26 20:17 ` [PATCH v4 1/3] rust: Add soc_device support Matthew Maurer
2025-12-26 20:17 ` [PATCH v4 2/3] docs: ABI: sysfs-devices-soc: Fix swapped sample values Matthew Maurer
2025-12-28 18:12 ` Danilo Krummrich
2025-12-28 20:12 ` Matthew Maurer
2025-12-29 14:07 ` Danilo Krummrich [this message]
2025-12-26 20:17 ` [PATCH v4 3/3] rust: Add SoC Driver Sample Matthew Maurer
2025-12-27 15:53 ` Kari Argillander
2025-12-27 18:49 ` Matthew Maurer
2025-12-28 18:11 ` [PATCH v4 0/3] Support exporting SoC info from Rust 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=DFARC0ZSLQUS.30H5E9NMYJGJ9@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=mmaurer@google.com \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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.