From: Nick Clifton <nickc@redhat.com>
To: Cupertino Miranda <Cupertino.Miranda@synopsys.com>,
"binutils@sourceware.org" <binutils@sourceware.org>
Cc: Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>,
Francois Bedard <Francois.Bedard@synopsys.com>
Subject: Re: [PATCH ARC 5/5] PLT content endianess awareness
Date: Tue, 05 Apr 2016 14:32:00 -0000 [thread overview]
Message-ID: <5703CC86.3090900@redhat.com> (raw)
In-Reply-To: <EB86EB452ADE4B44B294F7149B8A2777021A5E41@DE02WEMBXB.internal.synopsys.com>
Hi Cupertino,
> bfd/ChangeLog:
>
> Cupertino Miranda <cmiranda@synopsys.com>
> elf32-arc.c (plt_do_relocs_for_symbol): Changed.
> (relocate_plt_for_entry): Likewise.
Approved - please apply.
Cheers
Nick
next prev parent reply other threads:[~2016-04-05 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 12:51 Cupertino Miranda
2016-04-05 14:32 ` Nick Clifton [this message]
2016-04-05 15:28 ` Claudiu Zissulescu
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=5703CC86.3090900@redhat.com \
--to=nickc@redhat.com \
--cc=Claudiu.Zissulescu@synopsys.com \
--cc=Cupertino.Miranda@synopsys.com \
--cc=Francois.Bedard@synopsys.com \
--cc=binutils@sourceware.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).