From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] toolchain-external: CodeSourcery NiosII 2015.11 affected by PR19405
Date: Sat, 20 Feb 2016 13:48:22 +0100 [thread overview]
Message-ID: <56C86096.4060207@gmail.com> (raw)
In-Reply-To: <87fuwrxc3z.fsf@dell.be.48ers.dk>
Hi Peter,
Le 17/02/2016 22:26, Peter Korsgaard a ?crit :
>>>>>> "Romain" == Romain Naour <romain.naour@gmail.com> writes:
> > Fixes:
> > http://autobuild.buildroot.net/results/ee562524c5b12191e584ceae89006c5a5103e700
>
> > Signed-off-by: Romain Naour <romain.naour@gmail.com>
> > ---
> > package/grantlee/Config.in | 1 +
> > package/opencv/Config.in | 1 +
> > package/opencv3/Config.in | 1 +
> > package/pinentry/Config.in | 1 +
> > package/poppler/Config.in | 1 +
> > package/qt/Config.in | 7 +++++++
>
> Hmm, why are we only adding a comment to qt and not all these other
> packages?
I wasn't sure if we want to add a comment for a toolchain bug.
Hopefully the list of packages affected by this bug is not so long.
>
> It would be good to add a link to the upstream bugtracker in the commit
> description / where the kconfig symbol is added.
See, v2 http://patchwork.ozlabs.org/patch/585613/
Sorry, I forgot to add v2 in the tittle :-/
Best regards,
Romain
>
>
prev parent reply other threads:[~2016-02-20 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 22:33 [Buildroot] [PATCH 1/2] toolchain-external: CodeSourcery NiosII 2015.11 affected by PR19405 Romain Naour
2016-02-12 22:33 ` [Buildroot] [PATCH 2/2] package/binutils-2.25.1: backport upstream patch for PR19405 Romain Naour
2016-02-17 21:29 ` Peter Korsgaard
2016-02-17 21:26 ` [Buildroot] [PATCH 1/2] toolchain-external: CodeSourcery NiosII 2015.11 affected by PR19405 Peter Korsgaard
2016-02-20 12:48 ` Romain Naour [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=56C86096.4060207@gmail.com \
--to=romain.naour@gmail.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.