From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Boqun Feng" <boqun.feng@gmail.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Benno Lossin" <lossin@kernel.org>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"Gary Guo" <gary@garyguo.net>, "Miguel Ojeda" <ojeda@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Trevor Gross" <tmgross@umich.edu>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Yury Norov" <yury.norov@gmail.com>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: [PATCH V2 0/2] rust: Introduce CpuId and fix cpumask doctest
Date: Mon, 9 Jun 2025 16:21:04 +0530 [thread overview]
Message-ID: <cover.1749463570.git.viresh.kumar@linaro.org> (raw)
Hello,
Here is another attempt at fixing the cpumask doctest. This series creates a new
abstraction `CpuId`, which is used to write a cleaner cpumask example which
doesn't fail in those corner cases.
--
Viresh
V1->V2:
- Introduce CpuId.
- Use CpuId in cpufreq, opp, cpumask abstractions.
- Fix cpumask example.
Viresh Kumar (2):
rust: cpu: Introduce CpuId abstraction
rust: Use CpuId in place of raw CPU numbers
drivers/cpufreq/rcpufreq_dt.rs | 4 +-
rust/kernel/cpu.rs | 106 ++++++++++++++++++++++++++++++++-
rust/kernel/cpufreq.rs | 27 ++++++---
rust/kernel/cpumask.rs | 51 +++++++++++-----
4 files changed, 161 insertions(+), 27 deletions(-)
base-commit: 19272b37aa4f83ca52bdf9c16d5d81bdd1354494
--
2.31.1.272.g89b43f80a514
next reply other threads:[~2025-06-09 10:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 10:51 Viresh Kumar [this message]
2025-06-09 10:51 ` [PATCH V2 1/2] rust: cpu: Introduce CpuId abstraction Viresh Kumar
2025-06-09 11:18 ` Viresh Kumar
2025-06-09 14:04 ` Boqun Feng
2025-06-10 8:39 ` Viresh Kumar
2025-06-09 12:01 ` Miguel Ojeda
2025-06-10 6:07 ` Viresh Kumar
2025-06-10 9:43 ` Miguel Ojeda
2025-06-10 10:18 ` Viresh Kumar
2025-06-10 10:23 ` Miguel Ojeda
2025-06-10 10:00 ` Viresh Kumar
2025-06-10 10:14 ` Miguel Ojeda
2025-06-10 10:21 ` Miguel Ojeda
2025-06-10 10:38 ` Viresh Kumar
2025-06-10 10:19 ` Viresh Kumar
2025-06-10 10:50 ` Miguel Ojeda
2025-06-09 10:51 ` [PATCH V2 2/2] rust: Use CpuId in place of raw CPU numbers Viresh Kumar
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=cover.1749463570.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tmgross@umich.edu \
--cc=vincent.guittot@linaro.org \
--cc=yury.norov@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
all inboxes | Powered by JetHome®