From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>,
GLIBC Devel <libc-alpha@sourceware.org>
Cc: cltang@codesourcery.com, Carlos O'Donell <carlos@redhat.com>,
arjun@redhat.com
Subject: Re: 2.31: glibc master is now kinda, sorta, frozen
Date: Tue, 31 Dec 2019 13:53:57 -0300 [thread overview]
Message-ID: <4f7aabd7-29e9-2dd1-1fca-634b57d2f6a4@linaro.org> (raw)
In-Reply-To: <c590370f-f0b0-e653-1cc1-89183a802011@gotplt.org>
On 31/12/2019 13:29, Siddhesh Poyarekar wrote:
>
> - vDSO refactor and fixes
> https://sourceware.org/ml/libc-alpha/2019-12/msg00597.html
>
> Adhemerval, I see some reviews and change requests. Are you waiting for
> reviews on the rest of your patches or do you intend to post a v3
> patchset? I can help with reviews on Thursday if nobody gets to it by then.
I will check the review already done and send updated versions, thanks
for checking on it.
>
> - Add libm_alias_finite for _finite symbols
> https://sourceware.org/ml/libc-alpha/2019-10/msg00627.html
> It moves the _finite symbol to compat symbols and not enable them
> for newer architectures.
>
> Adhemerval, would you be OK with dropping this off the blocker list if a
> review suggests that the patchset needs an update? I'll do a review on
> Thursday and if there are no changes needed, you can push it in.
> However if the patchset needs changes, I'll help with reviews of the
> updated patchset too, but you can commit after the 2.31 release. Does
> that sound reasonable?
I will be around on Thursday and Friday, so if see anything need change
we can try to sort this out by Friday and if by then it is not already
ready I will postpone to 2.31.
next prev parent reply other threads:[~2019-12-31 16:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-31 16:29 2.31: glibc master is now kinda, sorta, frozen Siddhesh Poyarekar
2019-12-31 16:53 ` Adhemerval Zanella [this message]
2019-12-31 16:59 ` Adhemerval Zanella
2019-12-31 17:05 ` Rafal Luzynski
2020-01-06 15:41 ` Chung-Lin Tang
2020-01-06 15:46 ` Siddhesh Poyarekar
2020-01-07 9:07 ` Chung-Lin Tang
2020-01-07 22:15 ` Carlos O'Donell
2020-01-06 16:18 ` Arjun Shankar
2020-01-06 16:22 ` Siddhesh Poyarekar
2020-01-06 18:08 ` Arjun Shankar
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=4f7aabd7-29e9-2dd1-1fca-634b57d2f6a4@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=arjun@redhat.com \
--cc=carlos@redhat.com \
--cc=cltang@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.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).