[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250729-regulator-send-sync-v1-0-8bcbd546b940@collabora.com>
Date: Tue, 29 Jul 2025 14:31:39 -0300
From: Daniel Almeida <daniel.almeida@...labora.com>
To: Liam Girdwood <lgirdwood@...il.com>, Mark Brown <broonie@...nel.org>,
Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <lossin@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
Danilo Krummrich <dakr@...nel.org>
Cc: linux-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org,
Daniel Almeida <daniel.almeida@...labora.com>
Subject: [PATCH 0/2] rust: regulator: relax a few constraints on
Regulator<T>
This series implement two related changes to address a bit of an oversight
on my end on the initial patch for the Regulator abstraction. Note that
this is not a fix, as it just relaxes the constraints on the previous code
as it is safe to do so.
Patch 1 removes some needless &mut self for functions that already provide
their own locking on the C side.
Patch 2 implements Send and Sync. In particular, there is no reason for
Regulator<T> not to be Send, and as discussed above, it is naturally Sync.
This is based on linux-next for now, I am waiting for 6.17-rc1 to be out in
order to rebase.
---
Daniel Almeida (2):
rust: regulator: remove needless &mut from member functions
rust: regulator: implement Send and Sync for Regulator<T>
rust/kernel/regulator.rs | 26 +++++++++++++++++---------
1 file changed, 17 insertions(+), 9 deletions(-)
---
base-commit: 54efec8782214652b331c50646013f8526570e8d
change-id: 20250729-regulator-send-sync-94d4a7a61eff
Best regards,
--
Daniel Almeida <daniel.almeida@...labora.com>
Powered by blists - more mailing lists