[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20241023.130152.200800395770389333.fujita.tomonori@gmail.com>
Date: Wed, 23 Oct 2024 13:01:52 +0900 (JST)
From: FUJITA Tomonori <fujita.tomonori@...il.com>
To: andrew@...n.ch, anna-maria@...utronix.de, frederic@...nel.org,
tglx@...utronix.de, jstultz@...gle.com, sboyd@...nel.org
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, arnd@...db.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v3 0/8] rust: Add IO polling
On Fri, 18 Oct 2024 16:26:54 +0200
Andrew Lunn <andrew@...n.ch> wrote:
> On Wed, Oct 16, 2024 at 12:52:05PM +0900, FUJITA Tomonori wrote:
>> polls periodically until a condition is met or a timeout is reached.
>> By using the function, the 8th patch fixes QT2025 PHY driver to sleep
>> until the hardware becomes ready.
>>
>> As a result of the past discussion, this introduces a new type
>> representing a span of time instead of using core::time::Duration or
>> time::Ktime.
>>
>> Unlike the old rust branch, This adds a wrapper for fsleep() instead
>> of msleep(). fsleep() automatically chooses the best sleep method
>> based on a duration.
>
> This patchset is > 95% time handling, and only a small part
> networking. So i'm not sure netdev is the correct subsystem to merge
> this.
The time handling code became much bigger than I expected.
I'll send the next version for the tip tree.
TIME-KEEPING/TIMERS maintainers, would you prefer this to go through
the rust tree?
Powered by blists - more mailing lists