public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Alistair Francis <alistair.francis@wdc.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH v5 3/8] time: Add a __itimerval64 struct
Date: Fri, 27 Mar 2020 14:01:38 -0300	[thread overview]
Message-ID: <7bd73378-870a-09a5-299e-8cb12d3a40d5@linaro.org> (raw)
In-Reply-To: <20200303175355.15770-4-alistair.francis@wdc.com>



On 03/03/2020 14:53, Alistair Francis wrote:
> Add a __itimerval64 which always uses a 64-bit time_t.
> 
> Reviewed-by: Lukasz Majewski <lukma@denx.de>


LGTM, thanks.

Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>

> ---
>  include/time.h | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/include/time.h b/include/time.h
> index 927b1ed587..e70258e8e3 100644
> --- a/include/time.h
> +++ b/include/time.h
> @@ -110,6 +110,7 @@ struct __timeval64
>  
>  #if __TIMESIZE == 64
>  # define __utimbuf64 utimbuf
> +# define __itimerval64 itimerval
>  #else
>  /* The glibc Y2038-proof struct __utimbuf64 structure for file's access
>     and modification time values.  */
> @@ -118,6 +119,12 @@ struct __utimbuf64
>    __time64_t actime;		/* Access time.  */
>    __time64_t modtime;		/* Modification time.  */
>  };
> +/* The glibc's internal representation of the struct itimerval.  */
> +struct __itimerval64
> +{
> +  struct __timeval64 it_interval;
> +  struct __timeval64 it_value;
> +};
>  #endif
>  
>  #if __TIMESIZE == 64
> 

Ok.

  reply	other threads:[~2020-03-27 17:01 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03 18:01 [PATCH v5 0/8] Always use 32-bit time_t for certain syscalls Alistair Francis
2020-03-03 18:01 ` [PATCH v5 5/8] linux: Use long time_t __getitimer/__setitimer Alistair Francis
2020-03-27 18:09   ` Adhemerval Zanella
2020-03-27 18:21     ` Alistair Francis
2020-03-03 18:01 ` [PATCH v5 1/8] sysv/linux: Rename alpha functions to be alpha specific Alistair Francis
2020-03-05  9:51   ` Lukasz Majewski
2020-03-05 21:38     ` Zack Weinberg
2020-03-09 22:16       ` Alistair Francis
2020-03-12 18:45         ` Alistair Francis
2020-03-18 19:46           ` Alistair Francis
2020-03-24  7:33             ` Lukasz Majewski
2020-03-24 23:58               ` Alistair Francis
2020-03-27 16:15                 ` Adhemerval Zanella
2020-03-27 16:25                   ` Alistair Francis
2020-03-27 16:46   ` Adhemerval Zanella
2020-03-03 18:01 ` [PATCH v5 6/8] resource: Add a __rusage64 struct Alistair Francis
2020-03-27 18:14   ` Adhemerval Zanella
2020-03-03 18:01 ` [PATCH v5 7/8] linux: Use long time_t for wait4/getrusage Alistair Francis
2020-03-27 18:31   ` Adhemerval Zanella
2020-03-27 18:42     ` Alistair Francis
2020-04-04 14:52   ` Andreas Schwab
2020-03-03 18:01 ` [PATCH v5 2/8] time: Add a timeval with a 32-bit tv_sec and tv_usec Alistair Francis
2020-03-27 17:00   ` Adhemerval Zanella
2020-03-03 18:01 ` [PATCH v5 3/8] time: Add a __itimerval64 struct Alistair Francis
2020-03-27 17:01   ` Adhemerval Zanella [this message]
2020-03-03 18:01 ` [PATCH v5 8/8] sysv/alpha: Use generic __timeval32 and helpers Alistair Francis
2020-04-01 16:57   ` Adhemerval Zanella
2020-04-01 16:54     ` Alistair Francis
2020-03-03 18:01 ` [PATCH v5 4/8] sysv: Define __KERNEL_OLD_TIMEVAL_MATCHES_TIMEVAL64 Alistair Francis
2020-03-27 17:58   ` Adhemerval Zanella
2020-03-27 18:36     ` Alistair Francis
2020-04-04 13:58 ` [PATCH v5 0/8] Always use 32-bit time_t for certain syscalls Andreas Schwab
2020-04-06 13:24   ` Adhemerval Zanella
2020-04-06 14:03     ` Andreas Schwab
2020-04-06 16:16       ` Adhemerval Zanella
2020-04-06 17:07         ` Andreas Schwab
2020-04-06 17:34           ` Adhemerval Zanella
2020-04-06 17:43             ` Adhemerval Zanella
2020-04-06 17:48             ` Andreas Schwab
2020-04-06 17:45               ` Alistair Francis
2020-04-06 18:02                 ` Alistair Francis
2020-04-06 18:21                   ` Adhemerval Zanella

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=7bd73378-870a-09a5-299e-8cb12d3a40d5@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=alistair.francis@wdc.com \
    --cc=libc-alpha@sourceware.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).