From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bfin: disable newer binutils for internal toolchain
Date: Tue, 2 Sep 2014 09:11:50 +0200 [thread overview]
Message-ID: <20140902091150.33c30efa@free-electrons.com> (raw)
In-Reply-To: <20140901195817.GU30210@waldemar-brodkorb.de>
Dear Waldemar Brodkorb,
On Mon, 1 Sep 2014 21:58:18 +0200, Waldemar Brodkorb wrote:
> > Could you report the bug to upstream binutils? I'd like to be able to
> > get rid of binutils 2.22 at some point.
> >
> > Thanks a lot!
>
> Done:
> https://sourceware.org/bugzilla/show_bug.cgi?id=17334
Great. Could you respin a new version of your patch that references
this bug report in the comment, such as:
# bfin disabled due to
# https://sourceware.org/bugzilla/show_bug.cgi?id=17334
config ...
depends on !BR2_bfin
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-09-02 7:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-31 8:24 [Buildroot] [PATCH] bfin: disable newer binutils for internal toolchain Waldemar Brodkorb
2014-08-31 12:41 ` Thomas Petazzoni
2014-09-01 19:58 ` Waldemar Brodkorb
2014-09-02 7:11 ` 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=20140902091150.33c30efa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox