[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72n0v7jinSyO85vorYRFB=y5NH5roW4xLRjwZz+DFJ5QSQ@mail.gmail.com>
Date: Mon, 16 Jun 2025 22:40:08 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: onur-ozkan <work@...rozkan.dev>, Viresh Kumar <viresh.kumar@...aro.org>
Cc: linux-clk@...r.kernel.org, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org, mturquette@...libre.com, sboyd@...nel.org,
ojeda@...nel.org, alex.gaynor@...il.com, boqun.feng@...il.com,
gary@...yguo.net, bjorn3_gh@...tonmail.com, lossin@...nel.org,
a.hindborg@...nel.org, aliceryhl@...gle.com, tmgross@...ch.edu,
dakr@...nel.org
Subject: Re: [PATCH] Various improvements on clock abstractions
On Mon, Jun 16, 2025 at 10:01 PM onur-ozkan <work@...rozkan.dev> wrote:
>
> Signed-off-by: onur-ozkan <work@...rozkan.dev>
Should this be "Onur Özkan"? Apologies if not -- I am just asking
because the SoB typically uses the full name as usually written, and I
saw it in Zulip spelled differently.
Cc'ing Viresh, since he introduced the file.
On the changes themselves, the `const fn` one seems obvious.
The constants one is OK, though we could perhaps have a `units.h`
equivalent eventually.
The `map_or` is up to style, though I am not sure why you say "nested
if-else blocks" in the commit message, i.e. what is nested?
(By the way, this could (or not) have been split into different
patches -- it is up to the maintainers/reviewers, and it depends on
how complex a given patch is and other factors, but I thought I would
mention it just in case you thought it needed to be one.)
Thanks!
Cheers,
Miguel
Powered by blists - more mailing lists