All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-05-16
Date: Thu, 19 May 2016 10:26:47 -0300	[thread overview]
Message-ID: <573DBF17.3070406@zacarias.com.ar> (raw)
In-Reply-To: <20160517153611.2a3b4199@free-electrons.com>

On 17/05/16 10:36, Thomas Petazzoni wrote:

>>           arm |                 collectd-5.5.1 | NOK | http://autobuild.buildroot.net/results/80a75aaebd55fca1220048d1d4dfb434ce4d9804/
>>        x86_64 |                 collectd-5.5.1 | NOK | http://autobuild.buildroot.net/results/ae1e3a33a1c2b7433ca7a04659467e2017756b00/
>
> Gustavo, any solution in sight for this collectd problem?

Hi.
This is the same problem that was fixed for connman in 0dece985, fixed 
in linux via 4a91cb61.
The problem is that the connman fix breaks the proper fix in the kernel, 
and now that 4.5.5 and 4.6 are out i think the best approach is to bump 
the 4.5.x series for the release and drop the connman patch.
This has the side-effect of making connman/collectd with iptables and 
possibly some other netfilter-wielding code to be effectively broken for 
4.5.0 -> 4.5.4 headers though, but as long as we don't ship these in a 
release i think we should genrally be fine.
Regarding external toolchains time will tell, but any package patches we 
make about this will likely fall on silent ears upstream.
http://patchwork.ozlabs.org/patch/624067/ and 
http://patchwork.ozlabs.org/patch/624068/ address this.
Regards.

  parent reply	other threads:[~2016-05-19 13:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-05-16 Thomas Petazzoni
2016-05-17 13:36 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-05-17 13:53   ` Rodrigo Rebello
2016-05-17 15:13   ` gwenhael.goavec
2016-05-17 15:20     ` Thomas Petazzoni
2016-05-18  7:09       ` gwenhael.goavec
2016-05-18 19:40         ` Arnout Vandecappelle
2016-05-18 21:54           ` Thomas Petazzoni
2016-05-18 22:15             ` Arnout Vandecappelle
2016-05-17 16:27   ` Bernd Kuhls
2016-05-17 18:47   ` Bernd Kuhls
2016-05-17 18:56   ` Geoff Levand
2016-05-17 19:34     ` Thomas Petazzoni
2016-05-17 20:15       ` Geoff Levand
2016-05-17 21:03   ` Yegor Yefremov
2016-05-17 21:06     ` Yegor Yefremov
2016-05-18 19:33   ` Samuel Martin
2016-05-19 13:26   ` Gustavo Zacarias [this message]
2016-05-19 18:52   ` Gustavo Zacarias
2016-05-19 21:31     ` Arnout Vandecappelle
2016-05-20  7:35       ` Thomas Petazzoni
2016-05-25 14:44   ` Clayton Shotwell
2016-06-17  1:21   ` Ben Boeckel
2016-06-17  2:11     ` Ben Boeckel

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=573DBF17.3070406@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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.