Re: [PATCH] rust: clk: document overflow panics in `Hertz` constructors

[Brian Masney <bmasney@redhat.com>]

On Mon, Sep 21, 2026 at 06:08:46PM +0200, Miguel Ojeda wrote:
> On Mon, Sep 21, 2026 at 5:51 PM Alice Ryhl <aliceryhl@google.com> wrote:
> >
> > My understanding is that the "default" way patches land is that the
> > subsystem also takes Rust patches related to the subsystem, and that
> > the rust tree is a fallback tree.
> 
> Indeed, the idea on how we suggest setting up the `MAINTAINERS`
> entries is that, by default, maintainers keep control of both sides
> (they are the experts, after all) and that, hopefully, they get more
> involved on the Rust side etc.
> 
> It makes sense for reworking the subsystem, too, since it may happen
> that a rework on the C side may need adjustments on the Rust side etc.
> 
> The file is already under "COMMON CLK FRAMEWORK", so in this instance
> it seems fine.
> 
> Brian: in case you want it (but it wouldn't be needed!):
> 
> Acked-by: Miguel Ojeda <ojeda@kernel.org>
> 
> As Alexandre said, we may want to rework how these work (instead of
> panicking), but documenting helps for now (and whether this counts as
> a Fix or not is, I guess, up to what you usually do in your
> subsystem).
> 
> I hope that helps!

Sounds good, I'll pick this up.

Learning Rust is something that I want to start to do this coming
Winter. I have an existing userspace project that I'm going to convert
from python to rust.

Brian