From: Igor Korotin <igor.korotin.linux@gmail.com>
To: ojeda@kernel.org, alex.gaynor@gmail.com, rafael@kernel.org,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org, linux-acpi@vger.kernel.org
Cc: boqun.feng@gmail.com, gary@garyguo.net, bjorn3_gh@protonmail.com,
benno.lossin@proton.me, a.hindborg@kernel.org,
aliceryhl@google.com, tmgross@umich.edu, dakr@kernel.org,
lenb@kernel.org, wedsonaf@gmail.com, viresh.kumar@linaro.org,
alex.hung@amd.com, dingxiangfei2009@gmail.com
Subject: [PATCH v5 5/6] rust: cpufreq: Remove unnecessary `of` dependency in cpufreq example
Date: Wed, 11 Jun 2025 18:53:53 +0100 [thread overview]
Message-ID: <20250611175353.803835-1-igor.korotin.linux@gmail.com> (raw)
In-Reply-To: <20250611174034.801460-1-igor.korotin.linux@gmail.com>
Drop the explicit `use of` and `OF_ID_TABLE = None` assignment in the
cpufreq driver registration example.
Since `Adapter::OF_ID_TABLE` now defaults to `None`, drivers that do
not require OpenFirmware matching no longer need to import `of` or
define the constant explicitly.
Signed-off-by: Igor Korotin <igor.korotin.linux@gmail.com>
---
rust/kernel/cpufreq.rs | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/rust/kernel/cpufreq.rs b/rust/kernel/cpufreq.rs
index b0a9c6182aec..789c4a8936ab 100644
--- a/rust/kernel/cpufreq.rs
+++ b/rust/kernel/cpufreq.rs
@@ -842,7 +842,7 @@ fn register_em(_policy: &mut Policy) {
/// c_str,
/// device::{Core, Device},
/// macros::vtable,
-/// of, platform,
+/// platform,
/// sync::Arc,
/// };
/// struct SampleDevice;
@@ -887,7 +887,6 @@ fn register_em(_policy: &mut Policy) {
///
/// impl platform::Driver for SampleDriver {
/// type IdInfo = ();
-/// const OF_ID_TABLE: Option<of::IdTable<Self::IdInfo>> = None;
///
/// fn probe(
/// pdev: &platform::Device<Core>,
--
2.43.0
next prev parent reply other threads:[~2025-06-11 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 17:40 [PATCH v5 0/6] rust: Add ACPI match table support for Rust drivers Igor Korotin
2025-06-11 17:44 ` [PATCH v5 1/6] rust: acpi: add `acpi::DeviceId` abstraction Igor Korotin
2025-06-11 17:46 ` [PATCH v5 2/6] rust: driver: Consolidate `Adapter::of_id_info` methods using `#[cfg]` Igor Korotin
2025-06-11 17:48 ` [PATCH v5 3/6] rust: driver: Add ACPI id table support to Adapter trait Igor Korotin
2025-06-11 17:51 ` [PATCH v5 4/6] rust: platform: Add ACPI match table support to `Driver` trait Igor Korotin
2025-06-11 21:28 ` Danilo Krummrich
2025-06-11 17:53 ` Igor Korotin [this message]
2025-06-11 21:40 ` [PATCH v5 5/6] rust: cpufreq: Remove unnecessary `of` dependency in cpufreq example Danilo Krummrich
2025-06-11 17:56 ` [PATCH v5 6/6] samples: rust: add ACPI match table example to platform driver Igor Korotin
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=20250611175353.803835-1-igor.korotin.linux@gmail.com \
--to=igor.korotin.linux@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=alex.hung@amd.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=dingxiangfei2009@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=viresh.kumar@linaro.org \
--cc=wedsonaf@gmail.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).