[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87ple7i7a8.fsf@kernel.org>
Date: Fri, 11 Jul 2025 08:13:51 +0200
From: Andreas Hindborg <a.hindborg@...nel.org>
To: "FUJITA Tomonori" <fujita.tomonori@...il.com>
Cc: <miguel.ojeda.sandonis@...il.com>, <alex.gaynor@...il.com>,
<ojeda@...nel.org>, <aliceryhl@...gle.com>, <anna-maria@...utronix.de>,
<bjorn3_gh@...tonmail.com>, <boqun.feng@...il.com>, <dakr@...nel.org>,
<frederic@...nel.org>, <gary@...yguo.net>, <jstultz@...gle.com>,
<linux-kernel@...r.kernel.org>, <lossin@...nel.org>,
<lyude@...hat.com>, <rust-for-linux@...r.kernel.org>,
<sboyd@...nel.org>, <tglx@...utronix.de>, <tmgross@...ch.edu>
Subject: Re: [PATCH v3 0/5] rust: time: Convert hrtimer to use Instant and
Delta
"FUJITA Tomonori" <fujita.tomonori@...il.com> writes:
> On Thu, 10 Jul 2025 13:59:17 +0200
> Andreas Hindborg <a.hindborg@...nel.org> wrote:
>
>> This was discussed [1] and consensus was reached that `as_*` iwth pass
>> by value plus a `Copy` bound on the trait is the way to go for this
>> method.
>>
>> [1] https://hackmd.io/ZXXSbxxQRpiWzX61sJFlcg?view#API-Naming-guidelines-for-conversion-functions
>
> Great, thanks!
>
> Would you like me to send a patch for something ― for example, a patch
> that applies the above changes to the current timekeeping-next tree?
>
> Or would you prefer to reset timekeeping-next to an earlier commit for
> a cleaner history, and have me send a patchset based on that?
Yes, we should align the code, so if you can change all the `as_nanos`
to take by value, that would be great.
I already sent the PR for the 6.17 merge window, so please send a new
patch, then we can get it in the next cycle.
Best regards,
Andreas Hindborg
Powered by blists - more mailing lists