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:51:12 +0200	[thread overview]
Message-ID: <20160519165112.6a8799cf@free-electrons.com> (raw)
In-Reply-To: <573DCB2F.1020200@zacarias.com.ar>

Hello,

On Thu, 19 May 2016 11:18:23 -0300, Gustavo Zacarias wrote:

> Well, no, after bumping to 4.5.5 connman will go broken with the hacky 
> patch because it's incompatible with the kernel fix upstream.

Yes, but if we:

 1/ Apply your patch 1/2 which bumps to 4.5.5

 2/ Apply your patch 2/2 which removes the patch

 3/ Rebuild the pre-built Buildroot external toolchains that used 4.5.4
    headers

Then, the connman build failures should go away, right?

Thanks,

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

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