[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-man
Subject:    Re: [PATCH 2/4] poll.2, sigwaitinfo.2: fix struct timespec::tv_sec to be time_t, not long
From:       "Alejandro Colomar (man-pages)" <alx.manpages () gmail ! com>
Date:       2021-11-29 12:27:28
Message-ID: 74f9b43a-f843-6abe-523a-f1615aa37363 () gmail ! com
[Download RAW message or body]

As I said, I'd just replace those redefinitions by referencces to 
timespec(3).  The fact that these contained different types for tv_sec 
confirms my guess that not all of the repeated definitions were correct.

On 11/28/21 19:17, наб wrote:
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
> ---
>   man2/poll.2        | 2 +-
>   man2/sigwaitinfo.2 | 2 +-
>   2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/man2/poll.2 b/man2/poll.2
> index 620528ec7..a278efbcc 100644
> --- a/man2/poll.2
> +++ b/man2/poll.2
> @@ -329,7 +329,7 @@ This argument is a pointer to a structure of the following form:
>   .in +4n
>   .EX
>   struct timespec {
> -    long    tv_sec;         /* Seconds */
> +    time_t  tv_sec;         /* Seconds */
>       long    tv_nsec;        /* Nanoseconds [0 .. 999999999] */
>   };
>   .EE
> diff --git a/man2/sigwaitinfo.2 b/man2/sigwaitinfo.2
> index 716661479..226625e4e 100644
> --- a/man2/sigwaitinfo.2
> +++ b/man2/sigwaitinfo.2
> @@ -93,7 +93,7 @@ This argument is of the following type:
>   .in +4n
>   .EX
>   struct timespec {
> -    long    tv_sec;         /* Seconds */
> +    time_t  tv_sec;         /* Seconds */
>       long    tv_nsec;        /* Nanoseconds [0 .. 999999999] */
>   }
>   .EE
> 

-- 
Alejandro Colomar
Linux man-pages comaintainer; http://www.kernel.org/doc/man-pages/
[prev in list] [next in list] [prev in thread] [next in thread]