From: Vincent Chen <vincent.chen@sifive.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: Jim Wilson <jimw@sifive.com>,
GNU C Library <libc-alpha@sourceware.org>,
Nelson Chu <nelson.chu@sifive.com>,
Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH v2 0/2] riscv: add support for GNU indirect function
Date: Wed, 6 Jan 2021 08:53:56 +0800 [thread overview]
Message-ID: <CABvJ_xhcnX5ZbP0jpRC2r7W6LXUEOSeHuUdwVoqho3DswoG7iw@mail.gmail.com> (raw)
In-Reply-To: <d46405bd-af1e-6389-a8df-c02472bc269b@redhat.com>
On Tue, Jan 5, 2021 at 8:32 PM Carlos O'Donell <carlos@redhat.com> wrote:
>
> On 1/4/21 8:53 PM, Jim Wilson wrote:
> > On Sun, Jan 3, 2021 at 5:38 PM Vincent Chen <vincent.chen@sifive.com> wrote:
> >
> >> Gentle ping on this series. Thanks and happy new year.
> >>
> >
> > This is on the release blockers list at my request, so hopefully it will
> > get looked at before the release.
> > https://sourceware.org/glibc/wiki/Release/2.33#Release_blockers.3F
>
> The patches were discussed on the Monday patch review meeting.
>
> I've asked DJ to help move these along.
>
> I have confidence that we will get to them before the release.
>
Glad to hear this information. Thanks to the people who have given me
help on this patch set.
Best Regards
Vincent Chen
next prev parent reply other threads:[~2021-01-06 0:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 9:16 Vincent Chen
2020-12-15 9:16 ` [PATCH v2 1/2] riscv: support " Vincent Chen
2020-12-15 9:16 ` [PATCH v2 2/2] riscv: Initialize $gp before resolving the IRELATIVE relocation Vincent Chen
2021-01-04 1:38 ` [PATCH v2 0/2] riscv: add support for GNU indirect function Vincent Chen
2021-01-05 1:53 ` Jim Wilson
2021-01-05 3:13 ` Nelson Chu
2021-01-05 12:32 ` Carlos O'Donell
2021-01-06 0:53 ` Vincent Chen [this message]
2021-01-11 2:29 ` DJ Delorie
2021-01-11 7:34 ` Nelson Chu
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=CABvJ_xhcnX5ZbP0jpRC2r7W6LXUEOSeHuUdwVoqho3DswoG7iw@mail.gmail.com \
--to=vincent.chen@sifive.com \
--cc=carlos@redhat.com \
--cc=jimw@sifive.com \
--cc=libc-alpha@sourceware.org \
--cc=nelson.chu@sifive.com \
--cc=paul.walmsley@sifive.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).