public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@imgtec.com>
To: Alan Modra <amodra@gmail.com>
Cc: James Cowgill <James.Cowgill@imgtec.com>, <binutils@sourceware.org>
Subject: Re: [PATCH v2 0/2] PR ld/21334: `_bfd_elf_link_renumber_dynsyms' call fixes
Date: Wed, 26 Apr 2017 21:48:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.00.1704262225280.25796@tp.orcam.me.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.1704261335250.25796@tp.orcam.me.uk>

On Wed, 26 Apr 2017, Maciej W. Rozycki wrote:

> > >  As promised here is a mini patch series to address issues with calling 
> > > `_bfd_elf_link_renumber_dynsyms'.  See the individual descriptions for 
> > > details.
> > 
> > OK for both patches, thanks.
> 
>  Committed, thanks.

 And now backported to 2.28, after an additional test cycle due to the 
changes being more than just a mechanical patch merge.  Final patches 
posted for documentation purposes, for the same reason, and PR ld/21334 
now closed.

  Maciej

      reply	other threads:[~2017-04-26 21:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-24 19:12 Maciej W. Rozycki
2017-04-24 19:13 ` [PATCH v2 1/2] ELF/BFD: Limit `_bfd_elf_link_renumber_dynsyms' call in section GC Maciej W. Rozycki
2017-04-26 21:38   ` [committed 2.28 " Maciej W. Rozycki
2017-04-24 19:16 ` [PATCH v2 2/2] PR ld/21334: Always call `_bfd_elf_link_renumber_dynsyms' if required Maciej W. Rozycki
2017-04-26 21:39   ` [committed 2.28 " Maciej W. Rozycki
2017-04-26  8:22 ` [PATCH v2 0/2] PR ld/21334: `_bfd_elf_link_renumber_dynsyms' call fixes Alan Modra
2017-04-26 12:36   ` Maciej W. Rozycki
2017-04-26 21:48     ` Maciej W. Rozycki [this message]

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=alpine.DEB.2.00.1704262225280.25796@tp.orcam.me.uk \
    --to=macro@imgtec.com \
    --cc=James.Cowgill@imgtec.com \
    --cc=amodra@gmail.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).