Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 16:14:55 +0200	[thread overview]
Message-ID: <20160519161455.2bacf98f@free-electrons.com> (raw)
In-Reply-To: <573DC881.2030409@zacarias.com.ar>

Hello,

On Thu, 19 May 2016 11:06:57 -0300, Gustavo Zacarias wrote:

> Not right now since 4.6 is in -next, however it will if the stable 
> headers are bumped to 4.5.5.

Well, your patch 1/2 does:

-	default "4.4.10"	if BR2_KERNEL_HEADERS_4_4
-	default "4.5.4"		if BR2_KERNEL_HEADERS_4_5
+	default "4.4.11"	if BR2_KERNEL_HEADERS_4_4
+	default "4.5.5"		if BR2_KERNEL_HEADERS_4_5

So it should fix the thing, right?

However, it means I'd have to rebuild once again the Buildroot external
toolchains, at least the ones that use 4.5 kernel headers, right?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-05-19 14:14 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 [this message]
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
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=20160519161455.2bacf98f@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