From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] binutils: fix bfin problem
Date: Fri, 5 Aug 2016 21:28:55 +0200 [thread overview]
Message-ID: <20160805212855.2ad5b435@free-electrons.com> (raw)
In-Reply-To: <20160805192237.GE22524@waldemar-brodkorb.de>
Hello,
On Fri, 5 Aug 2016 21:22:37 +0200, Waldemar Brodkorb wrote:
> I am subscribed to binutils/gcc mailinglists and managed to already
> get some simple bugfixes added. But the times to get fixes in, might
> take some time.
I am not worried at all if things take time. Even if it takes 6 or 12
months, that's fine.
What worries me if it *never* gets fixed, because nobody works on it.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-08-05 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-31 8:26 [Buildroot] [PATCH] binutils: fix bfin problem Waldemar Brodkorb
2016-08-05 19:17 ` Thomas Petazzoni
2016-08-05 19:22 ` Waldemar Brodkorb
2016-08-05 19:28 ` 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=20160805212855.2ad5b435@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