Message ID | 20241016035214.2229-1-fujita.tomonori@gmail.com (mailing list archive) |
---|---|
Headers | show |
Series | rust: Add IO polling | expand |
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. I can give an Acked-by for the last patch, and i don't expect any merge conflicts. Andrew --- pw-bot: cr
On Fri, 18 Oct 2024 16:26:54 +0200 Andrew Lunn <andrew@lunn.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?