From: Mathieu Desnoyers via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha <libc-alpha@sourceware.org>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: [PATCH glibc 0/3] Restartable Sequences enablement
Date: Wed, 3 Jun 2020 08:27:27 -0400 (EDT) [thread overview]
Message-ID: <1704751537.51079.1591187247474.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <878sh4xshf.fsf@oldenburg2.str.redhat.com>
----- On Jun 3, 2020, at 8:07 AM, Florian Weimer fweimer@redhat.com wrote:
> This series unfortunately needs to be rebased (with conflicts) on
> current master.
I can rebase it again if you wish, but I would like to get some
consensus on the testing and documentation from other maintainers
first. Every now and then a new symbol is added into the master
branch for all architectures, and rebasing the rseq patches on top
of that at this point is wasted effort unless we are nearly ready
to merge.
>
> There is a new elf/tst-auditmany failure, showing bug 26076, but
> actually caused by bug 26075 (I think). I will attempt to work around
> these two issues, which are independent of the rseq changes.
OK
> As I said before, I would like to see some consensus if the level of
> testing and documentation in this series is appropriate for this
> feature.
Likewise,
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2020-06-03 12:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 18:51 [PATCH glibc 0/3] Restartable Sequences enablement Mathieu Desnoyers via Libc-alpha
2020-05-27 18:51 ` [PATCH glibc 1/3] glibc: Perform rseq registration at C startup and thread creation (v20) Mathieu Desnoyers via Libc-alpha
2020-06-03 12:05 ` Florian Weimer via Libc-alpha
2020-06-03 12:22 ` Mathieu Desnoyers via Libc-alpha
2020-06-03 12:31 ` Florian Weimer via Libc-alpha
2020-06-03 12:40 ` Mathieu Desnoyers via Libc-alpha
2020-06-03 17:22 ` Joseph Myers
2020-06-04 11:10 ` Mathieu Desnoyers via Libc-alpha
2020-06-04 17:46 ` Joseph Myers
2020-06-11 17:47 ` Mathieu Desnoyers via Libc-alpha
2020-06-11 20:26 ` Joseph Myers
2020-06-18 12:22 ` Szabolcs Nagy
2020-06-18 13:03 ` Mathieu Desnoyers via Libc-alpha
2020-06-22 15:33 ` Mathieu Desnoyers via Libc-alpha
2020-05-27 18:51 ` [PATCH glibc 2/3] Linux: Use rseq in sched_getcpu if available (v9) Mathieu Desnoyers via Libc-alpha
2020-05-27 18:51 ` [PATCH glibc 3/3] rseq registration tests (v11) Mathieu Desnoyers via Libc-alpha
2020-06-03 12:07 ` [PATCH glibc 0/3] Restartable Sequences enablement Florian Weimer via Libc-alpha
2020-06-03 12:27 ` Mathieu Desnoyers via Libc-alpha [this message]
2020-06-03 12:33 ` Florian Weimer via Libc-alpha
2020-06-03 13:40 ` Florian Weimer via Libc-alpha
2020-06-05 17:04 ` Mathieu Desnoyers via Libc-alpha
-- strict thread matches above, loose matches on Subject: below --
2020-05-01 2:14 Mathieu Desnoyers via Libc-alpha
2020-05-20 11:44 ` Florian Weimer via Libc-alpha
2020-05-25 13:52 ` Mathieu Desnoyers via Libc-alpha
2020-05-25 14:28 ` Florian Weimer via Libc-alpha
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=1704751537.51079.1591187247474.JavaMail.zimbra@efficios.com \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=mathieu.desnoyers@efficios.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).