From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] binutils: fix xtensa ld bug triggered by --gc-sections
Date: Sat, 16 May 2015 14:24:03 +0200 [thread overview]
Message-ID: <20150516142403.6351e042@free-electrons.com> (raw)
In-Reply-To: <1431578340-11753-1-git-send-email-jcmvbkbc@gmail.com>
Dear Max Filippov,
On Thu, 14 May 2015 07:38:58 +0300, Max Filippov wrote:
> Hi,
>
> this series backports binutils fix for xtensa ld and reverts old workaround
> for this bug.
>
> Max Filippov (2):
> binutils: fix xtensa ld bug triggered by --gc-sections
> Revert "kmod: disable --gc-sections ld option when building for
> xtensa"
Both patches applied, thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-05-16 12:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 4:38 [Buildroot] [PATCH 0/2] binutils: fix xtensa ld bug triggered by --gc-sections Max Filippov
2015-05-14 4:38 ` [Buildroot] [PATCH 1/2] " Max Filippov
2015-05-14 4:39 ` [Buildroot] [PATCH 2/2] Revert "kmod: disable --gc-sections ld option when building for xtensa" Max Filippov
2015-05-16 12:24 ` Thomas Petazzoni [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=20150516142403.6351e042@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.