From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Danilo Krummrich <dakr@kernel.org>
Cc: FUJITA Tomonori <tomo@flapping.org>,
Jiri Slaby <jirislaby@kernel.org>,
markus.probst@posteo.de, ojeda@kernel.org, a.hindborg@kernel.org,
acourbot@nvidia.com, aliceryhl@google.com,
bjorn3_gh@protonmail.com, boqun@kernel.org,
daniel.almeida@collabora.com, gary@garyguo.net,
lossin@kernel.org, tamird@kernel.org, tmgross@umich.edu,
work@onurozkan.dev, linux-serial@vger.kernel.org,
rust-for-linux@vger.kernel.org, fujita.tomonori@gmail.com
Subject: Re: [PATCH v3] rust: serdev: use Delta<Jiffy> for timeouts
Date: Wed, 18 Nov 2026 06:25:09 +0100 [thread overview]
Message-ID: <2026111857-boozy-hamper-7924@gregkh> (raw)
In-Reply-To: <DMXKAJKEIMFA.X1EWOKG0JRWG@kernel.org>
On Tue, Nov 17, 2026 at 03:39:22PM +0100, Danilo Krummrich wrote:
> (Cc: Greg, Jiri)
>
> On Tue Nov 17, 2026 at 12:07 PM CET, FUJITA Tomonori wrote:
> > On Tue, 3 Nov 2026 10:11:43 +0900
> > FUJITA Tomonori <tomo@flapping.org> wrote:
> >
> >> From: FUJITA Tomonori <fujita.tomonori@gmail.com>
> >>
> >> write_all() and wait_until_sent() take the timeout as a raw Jiffies,
> >> which is a c_ulong alias. The type does not show the unit.
> >>
> >> Take the timeout as Delta<Jiffy> instead.
> >>
> >> The C side treats a timeout of 0 as "wait indefinitely". The Rust API
> >> does not keep that meaning. A timeout of 0 or negative is rounded up
> >> to one jiffy. A caller that wants to wait indefinitely passes
> >> Delta::from_jiffies(isize::MAX). That value is MAX_SCHEDULE_TIMEOUT.
> >> The C side replaces 0 with MAX_SCHEDULE_TIMEOUT before it waits, so
> >> this gives the same wait as a timeout of 0 did before.
> >>
> >> Reviewed-by: Markus Probst <markus.probst@posteo.de>
> >> Signed-off-by: FUJITA Tomonori <fujita.tomonori@gmail.com>
> >
> > Gentle ping.
> >
> > Danilo, could you take this through driver-core? It applies cleanly to
> > driver-core-next.
>
> I think serdev stuff usually goes through TTY.
>
> Greg, can you please pick this up?
Will do when I catch up on serial patches, thanks.
greg k-h
prev parent reply other threads:[~2026-11-18 5:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 1:11 [PATCH v3] rust: serdev: use Delta<Jiffy> for timeouts FUJITA Tomonori
2026-11-03 1:17 ` sashiko-bot
2026-11-17 11:07 ` FUJITA Tomonori
2026-11-17 14:39 ` Danilo Krummrich
2026-11-18 5:25 ` Greg Kroah-Hartman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026111857-boozy-hamper-7924@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=jirislaby@kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=markus.probst@posteo.de \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=tomo@flapping.org \
--cc=work@onurozkan.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.