[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20241007.143707.787219256158321665.fujita.tomonori@gmail.com>
Date: Mon, 07 Oct 2024 14:37:07 +0900 (JST)
From: FUJITA Tomonori <fujita.tomonori@...il.com>
To: finn@...enk.dev
Cc: fujita.tomonori@...il.com, netdev@...r.kernel.org,
rust-for-linux@...r.kernel.org, andrew@...n.ch, hkallweit1@...il.com,
tmgross@...ch.edu, ojeda@...nel.org, alex.gaynor@...il.com,
gary@...yguo.net, bjorn3_gh@...tonmail.com, benno.lossin@...ton.me,
a.hindborg@...sung.com, aliceryhl@...gle.com, anna-maria@...utronix.de,
frederic@...nel.org, tglx@...utronix.de, arnd@...db.de,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v2 1/6] rust: time: Implement PartialEq and
PartialOrd for Ktime
On Sun, 06 Oct 2024 12:28:59 +0200
Fiona Behrens <finn@...enk.dev> wrote:
>> Implement PartialEq and PartialOrd trait for Ktime by using C's
>> ktime_compare function so two Ktime instances can be compared to
>> determine whether a timeout is met or not.
>
> Why is this only PartialEq/PartialOrd? Could we either document why or implement Eq/Ord as well?
Because what we need to do is comparing two Ktime instances so we
don't need them?
Powered by blists - more mailing lists