From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH v2] Align *utime*() with POSIX/glibc
Date: Tue, 26 Jan 2021 17:28:06 +0100 [thread overview]
Message-ID: <20210126162806.GR4393@calimero.vinschen.de> (raw)
In-Reply-To: <20210126141631.66748-1-sebastian.huber@embedded-brains.de>
On Jan 26 15:16, Sebastian Huber wrote:
> Change the prototypes to be in line with POSIX/glibc. 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/_default_fcntl.h | 2 +-
> newlib/libc/include/sys/stat.h | 4 ++--
> newlib/libc/include/sys/time.h | 6 +++---
> 3 files changed, 6 insertions(+), 6 deletions(-)
I pushed this together with a matching patch in Cygwin.
Hope that's ok.
Thanks,
Corinna
next prev parent reply other threads:[~2021-01-26 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 14:16 Sebastian Huber
2021-01-26 14:19 ` Sebastian Huber
2021-01-26 16:28 ` Corinna Vinschen [this message]
2021-10-05 15:33 [PATCH v2 0/4] Optimize red-black tree insert/extract Sebastian Huber
2021-10-05 15:33 ` [PATCH v2] Align *utime*() with POSIX/glibc Sebastian Huber
2021-10-05 15:35 ` 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=20210126162806.GR4393@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).