From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] connman: remove xtables build fix patch
Date: Thu, 19 May 2016 17:16:36 +0200 [thread overview]
Message-ID: <20160519171636.71e7164f@free-electrons.com> (raw)
In-Reply-To: <573DD413.1050603@zacarias.com.ar>
Hello,
On Thu, 19 May 2016 11:56:19 -0300, Gustavo Zacarias wrote:
> The only caveat would be people with toolchain headers 4.5.0 - 4.5.4 or
> any eventual external toolchain that ships that way (which by definition
> would be "broken").
Yes, understood. But I believe that's a reasonable trade-off. Building
a toolchain with 4.5 headers (and therefore running 4.5) is really being
bleeding-edge, so it's pretty unlikely to see many users doing that.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-19 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 13:25 [Buildroot] [PATCH 1/2] linux-headers: bump 3.14.x and 4.{4, 5}.x series Gustavo Zacarias
2016-05-19 13:25 ` [Buildroot] [PATCH 2/2] connman: remove xtables build fix patch Gustavo Zacarias
2016-05-19 14:06 ` Thomas Petazzoni
2016-05-19 14:06 ` Gustavo Zacarias
2016-05-19 14:14 ` Thomas Petazzoni
2016-05-19 14:18 ` Gustavo Zacarias
2016-05-19 14:51 ` Thomas Petazzoni
2016-05-19 14:56 ` Gustavo Zacarias
2016-05-19 15:16 ` Thomas Petazzoni [this message]
2016-05-21 11:17 ` [Buildroot] [PATCH 1/2] linux-headers: bump 3.14.x and 4.{4, 5}.x series Bernd Kuhls
2016-05-22 20:51 ` Thomas Petazzoni
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=20160519171636.71e7164f@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