From: Joseph Myers <joseph@codesourcery.com>
To: Fangrui Song <maskray@google.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] elf: Drop elf/tls-macros.h in favor of __thread and tls_model attributes [BZ #28152] [BZ #28205]
Date: Thu, 12 Aug 2021 15:36:48 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2108121536310.2672396@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20210811221150.mspqnhxlspumgjvg@google.com>
On Wed, 11 Aug 2021, Fangrui Song via Libc-alpha wrote:
> Thanks for the your comments. Do you have specific suggestion on this
> patch?
I do not have a specific suggestion on this patch.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2021-08-12 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 21:31 [PATCH] elf: Drop elf/tls-macros.h in favor of __thread and tls_model attributes [BZ #28152] [BZ #28205] Fangrui Song via Libc-alpha
2021-08-11 21:54 ` Joseph Myers
2021-08-11 22:11 ` Fangrui Song via Libc-alpha
2021-08-12 9:16 ` Szabolcs Nagy via Libc-alpha
2021-08-12 15:36 ` Joseph Myers [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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.22.394.2108121536310.2672396@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=maskray@google.com \
/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).