public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH 0/5] Synchronize <sys/cdefs.h> and <stdatomic.h> with FreeBSD
Date: Mon, 26 Oct 2020 10:51:33 +0100	[thread overview]
Message-ID: <20201026095133.GZ5492@calimero.vinschen.de> (raw)
In-Reply-To: <20201019155537.15290-1-sebastian.huber@embedded-brains.de>

On Oct 19 17:55, Sebastian Huber wrote:
> This patch set adds some changes after the last synchronization point with
> FreeBSD to Newlib.
> 
> dab (1):
>   Don't sanitize linker_set
> 
> jah (1):
>   amd64: prevent KCSan false positives on LAPIC mapping
> 
> jhb (1):
>   Make the system C11 atomics headers fully compatible with external
>     GCC.
> 
> mjg (1):
>   sys: clean up empty lines in .c and .h files
> 
> rlibby (1):
>   gcc: quiet Wattribute for no_sanitize("address")
> 
>  newlib/libc/include/stdatomic.h | 26 +++++++++++---------------
>  newlib/libc/include/sys/cdefs.h | 15 ++++++++++++++-
>  2 files changed, 25 insertions(+), 16 deletions(-)
> 
> -- 
> 2.26.2

LGTM, please push.


Thanks,
Corinna


      parent reply	other threads:[~2020-10-26  9:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 15:55 Sebastian Huber
2020-10-19 15:55 ` [PATCH 1/5] Make the system C11 atomics headers fully compatible with external GCC Sebastian Huber
2020-10-19 15:55 ` [PATCH 2/5] Don't sanitize linker_set Sebastian Huber
2020-10-19 15:55 ` [PATCH 3/5] gcc: quiet Wattribute for no_sanitize("address") Sebastian Huber
2020-10-19 15:55 ` [PATCH 4/5] sys: clean up empty lines in .c and .h files Sebastian Huber
2020-10-19 15:55 ` [PATCH 5/5] amd64: prevent KCSan false positives on LAPIC mapping Sebastian Huber
2020-10-26  9:51 ` Corinna Vinschen [this message]

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=20201026095133.GZ5492@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).