From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH] Align utimensat() and utimes() with POSIX
Date: Tue, 26 Jan 2021 13:35:08 +0100 [thread overview]
Message-ID: <20210126123508.GP4393@calimero.vinschen.de> (raw)
In-Reply-To: <20210125121000.72815-1-sebastian.huber@embedded-brains.de>
On Jan 25 13:10, Sebastian Huber wrote:
> Change the prototypes to be in line with POSIX. This may fix issues
> with new warnings produced by GCC 11.
>
> Signed-off-by: Sebastian Huber <sebastian.huber@embedded-brains.de>
> ---
> newlib/libc/include/sys/stat.h | 2 +-
> newlib/libc/include/sys/time.h | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/newlib/libc/include/sys/stat.h b/newlib/libc/include/sys/stat.h
> index 8769112b0..9eea7fc6e 100644
> --- a/newlib/libc/include/sys/stat.h
> +++ b/newlib/libc/include/sys/stat.h
> @@ -153,7 +153,7 @@ int fstatat (int, const char *__restrict , struct stat *__restrict, int);
> int mkdirat (int, const char *, mode_t);
> int mkfifoat (int, const char *, mode_t);
> int mknodat (int, const char *, mode_t, dev_t);
> -int utimensat (int, const char *, const struct timespec *, int);
> +int utimensat (int, const char *, const struct timespec [2], int);
> #endif
> #if __POSIX_VISIBLE >= 200809 && !defined(__INSIDE_CYGWIN__)
> int futimens (int, const struct timespec *);
> diff --git a/newlib/libc/include/sys/time.h b/newlib/libc/include/sys/time.h
> index 84a429bf2..fb46771d7 100644
> --- a/newlib/libc/include/sys/time.h
> +++ b/newlib/libc/include/sys/time.h
> @@ -414,7 +414,7 @@ struct itimerval {
> #include <time.h>
>
> __BEGIN_DECLS
> -int utimes (const char *__path, const struct timeval *__tvp);
> +int utimes (const char *, const struct timeval [2]);
>
> #if __BSD_VISIBLE
> int adjtime (const struct timeval *, struct timeval *);
> --
> 2.26.2
LGTM, but shouldn't futimens get changed as well?
And what about the BSD variants futimes and lutimes?
Thanks,
Corinna
next prev parent reply other threads:[~2021-01-26 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 12:10 Sebastian Huber
2021-01-26 12:35 ` Corinna Vinschen [this message]
2021-01-26 14:09 ` Sebastian Huber
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=20210126123508.GP4393@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@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).