On Tue, Oct 10, 2023 at 12:29:22PM +0200, Paweł Modrzejewski wrote:
> Make it possible to set timeout values bigger than 2.147 sec
> and print error message in case port_set_sync_rx_tmo() fails.
>
> Signed-off-by: Paweł Modrzejewski
Applied.
Thanks,
Richard
___
Yup, I'm observing this on 32-bit system. Even though my kernel
supports 64-bit time_t, nanoseconds are still signed long int there...
Thanks,
Pawel
wt., 10 paź 2023 o 12:42 Miroslav Lichvar napisał(a):
>
> On Tue, Oct 10, 2023 at 12:29:22PM +0200, Paweł Modrzejewski wrote:
> > Make it possible
On Tue, Oct 10, 2023 at 12:29:22PM +0200, Paweł Modrzejewski wrote:
> Make it possible to set timeout values bigger than 2.147 sec
> and print error message in case port_set_sync_rx_tmo() fails.
I think this limitation was specific to 32-bit systems that don't use
64-bit time_t.
> --- a/port.c
>
Make it possible to set timeout values bigger than 2.147 sec
and print error message in case port_set_sync_rx_tmo() fails.
Signed-off-by: Paweł Modrzejewski
---
port.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/port.c b/port.c
index 5803cd3..61d03d4 100644
--
