[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <06C4ED75-E370-4F19-B6BE-6D2455C94180@collabora.com>
Date: Thu, 4 Sep 2025 10:22:38 -0300
From: Daniel Almeida <daniel.almeida@...labora.com>
To: Alice Ryhl <aliceryhl@...gle.com>
Cc: Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Viresh Kumar <viresh.kumar@...aro.org>,
Miguel Ojeda <ojeda@...nel.org>,
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>,
Trevor Gross <tmgross@...ch.edu>,
Danilo Krummrich <dakr@...nel.org>,
linux-clk@...r.kernel.org,
rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] rust: clk: implement Send and Sync
> On 4 Sep 2025, at 10:07, Alice Ryhl <aliceryhl@...gle.com> wrote:
>
> On Thu, Sep 4, 2025 at 2:31 PM Daniel Almeida
> <daniel.almeida@...labora.com> wrote:
>> Can you base your change on top of [0]? Otherwise it will become stale rather
>> quickly, as this introduces new types, i.e.: Clk<Unprepared>, Clk<Prepared>
>> etc.
>>
>> I will push out a new version today.
>>
>> [0]: https://lore.kernel.org/rust-for-linux/20250729-clk-type-state-v1-1-896b53816f7b@collabora.com/
>
> I would suggest the reverse. If your series is based on top of mine,
> then this patch can land today regardless of how long it takes to
> finish the clk refactor.
>
> Alice
>
True,
Ok then:
Reviewed-by: Daniel Almeida <daniel.almeida@...labora.com>
Powered by blists - more mailing lists