From: Nick Clifton <nickc@redhat.com>
To: Stafford Horne <shorne@gmail.com>,
GNU Binutils <binutils@sourceware.org>
Cc: Openrisc <openrisc@lists.librecores.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH 0/8] OpenRISC BFD fixups for Glibc
Date: Tue, 19 May 2020 14:30:06 +0100 [thread overview]
Message-ID: <2c2a4907-bb08-a112-e716-bf6f2cef3642@redhat.com> (raw)
In-Reply-To: <20200514210018.2749462-1-shorne@gmail.com>
Hi Stafford,
> Stafford Horne (8):
> or1k: Fix static linking when with .rela.got relocations
> or1k: Fix dynamic TLS symbol flag
> or1k: Add TLS mask to handle multiple model access
> or1k: Fix issue with multiple PCREL relocations
> or1k: TLS offset to use tcb size and section alignment
> or1k: refactor: Rename p to sec_relocs
> or1k: refactor: Rename s to sgot and splt
> or1k: Add dynamic flag to tpoff
Patch series approved and applied. (Sorry for the delay...)
Cheers
Nick
next prev parent reply other threads:[~2020-05-19 13:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 21:00 Stafford Horne
2020-05-14 21:00 ` [PATCH 1/8] or1k: Fix static linking when with .rela.got relocations Stafford Horne
2020-05-14 21:00 ` [PATCH 2/8] or1k: Fix dynamic TLS symbol flag Stafford Horne
2020-05-14 21:00 ` [PATCH 3/8] or1k: Add TLS mask to handle multiple model access Stafford Horne
2020-05-14 21:00 ` [PATCH 4/8] or1k: Fix issue with multiple PCREL relocations Stafford Horne
2020-05-14 21:00 ` [PATCH 5/8] or1k: TLS offset to use tcb size and section alignment Stafford Horne
2020-05-14 21:00 ` [PATCH 6/8] or1k: refactor: Rename p to sec_relocs Stafford Horne
2020-05-14 21:00 ` [PATCH 7/8] or1k: refactor: Rename s to sgot and splt Stafford Horne
2020-05-14 21:00 ` [PATCH 8/8] or1k: Add dynamic flag to tpoff Stafford Horne
2020-05-19 13:30 ` Nick Clifton [this message]
2020-05-19 20:42 ` [PATCH 0/8] OpenRISC BFD fixups for Glibc Stafford Horne
2020-05-20 10:41 ` Nick Clifton
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=2c2a4907-bb08-a112-e716-bf6f2cef3642@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=openrisc@lists.librecores.org \
--cc=rth@twiddle.net \
--cc=shorne@gmail.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).