public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Adhemerval Zanella <azanella@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc/azanella/y2038] y2038: Add __USE_TIME_BITS64 support for struct utimbuf Date: Tue, 8 Jun 2021 20:48:45 +0000 (GMT) [thread overview] Message-ID: <20210608204845.15BF33985003@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=c3da822ff96e10de7e1b6864c5e4a049bd23e8f8 commit c3da822ff96e10de7e1b6864c5e4a049bd23e8f8 Author: Adhemerval Zanella <adhemerval.zanella@linaro.org> Date: Wed Feb 17 16:20:18 2021 -0300 y2038: Add __USE_TIME_BITS64 support for struct utimbuf The __USE_TIME_BITS64 is not defined internally yet. Reviewed-by: Lukasz Majewski <lukma@denx.de> Reviewed-by: Carlos O'Donell <carlos@redhat.com> Tested-by: Carlos O'Donell <carlos@redhat.com> Diff: --- io/utime.h | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/io/utime.h b/io/utime.h index df2299e406..c7612d0838 100644 --- a/io/utime.h +++ b/io/utime.h @@ -35,8 +35,13 @@ __BEGIN_DECLS /* Structure describing file times. */ struct utimbuf { +#ifdef __USE_TIME_BITS64 + __time64_t actime; /* Access time. */ + __time64_t modtime; /* Modification time. */ +#else __time_t actime; /* Access time. */ __time_t modtime; /* Modification time. */ +#endif }; /* Set the access and modification times of FILE to those given in
next reply other threads:[~2021-06-08 20:48 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-08 20:48 Adhemerval Zanella [this message] -- strict thread matches above, loose matches on Subject: below -- 2021-05-26 16:24 Adhemerval Zanella 2021-03-05 19:20 Adhemerval Zanella 2021-03-04 17:38 Adhemerval Zanella 2021-03-04 11:31 Adhemerval Zanella 2021-03-02 12:33 Adhemerval Zanella 2021-03-01 17:37 Adhemerval Zanella 2021-02-26 20:43 Adhemerval Zanella 2021-02-23 20:40 Adhemerval Zanella 2021-02-23 12:38 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=20210608204845.15BF33985003@sourceware.org \ --to=azanella@sourceware.org \ --cc=glibc-cvs@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: linkBe 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).