[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20241002.113401.1308475311422708175.fujita.tomonori@gmail.com>
Date: Wed, 02 Oct 2024 11:34:01 +0000 (UTC)
From: FUJITA Tomonori <fujita.tomonori@...il.com>
To: andrew@...n.ch
Cc: fujita.tomonori@...il.com, netdev@...r.kernel.org,
rust-for-linux@...r.kernel.org, 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
Subject: Re: [PATCH net-next v1 1/2] rust: add delay abstraction
On Tue, 1 Oct 2024 14:31:39 +0200
Andrew Lunn <andrew@...n.ch> wrote:
> On Tue, Oct 01, 2024 at 11:25:11AM +0000, FUJITA Tomonori wrote:
>> Add an abstraction for sleep functions in `include/linux/delay.h` for
>> dealing with hardware delays.
>>
>> The kernel supports several `sleep` functions for handles various
>
> s/for/which
Oops, thanks.
>> +/// Sleeps for a given duration.
>> +///
>> +/// Equivalent to the kernel's [`fsleep`] function, internally calls `udelay`,
>> +/// `usleep_range`, or `msleep`.
>
> Is it possible to cross reference
> Documentation/timers/timers-howto.rst ? fsleep() points to it, so it
> would e good if the Rust version also did.
>
> I would also document the units for the parameter. Is it picoseconds
> or centuries?
Rust's Duration is created from seconds and nanoseconds.
Powered by blists - more mailing lists