From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] toolchain: workaround musl/kernel headers conflict
Date: Wed, 16 Nov 2016 17:36:05 +0100 [thread overview]
Message-ID: <20161116173605.12aa2e5b@free-electrons.com> (raw)
In-Reply-To: <20161116162520.6quaqjt3fllqphma@sapphire.tkos.co.il>
Hello,
On Wed, 16 Nov 2016 18:25:20 +0200, Baruch Siach wrote:
> > So I believe we should apply your proposed workaround. However, I'm not
> > sure I want to take the risk of applying this to the master branch
> > (even though I agree it could fix some build failures). Are you OK with
> > applying it to the next branch?
>
> Of course. This is definitely not for master.
And any thoughts about my concerns to identify the packages that should
be re-enabled and patches that should be removed?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-11-16 16:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 13:27 [Buildroot] [PATCH v2 1/3] toolchain: workaround musl/kernel headers conflict Baruch Siach
2016-11-10 13:27 ` [Buildroot] [PATCH v2 2/3] Revert "bridge-utils: fix build with musl" Baruch Siach
2016-11-10 13:27 ` [Buildroot] [PATCH v2 3/3] Revert "norm: add patch to fix musl build" Baruch Siach
2016-11-13 21:33 ` [Buildroot] [PATCH v2 1/3] toolchain: workaround musl/kernel headers conflict Arnout Vandecappelle
2016-11-15 22:33 ` Thomas Petazzoni
2016-11-16 15:45 ` Baruch Siach
2016-11-16 15:55 ` Thomas Petazzoni
2016-11-16 16:25 ` Baruch Siach
2016-11-16 16:36 ` Thomas Petazzoni [this message]
2016-11-16 20:43 ` Baruch Siach
2016-11-16 22:30 ` Thomas Petazzoni
2017-05-17 13:33 ` Thomas Petazzoni
2017-05-18 4:57 ` Baruch Siach
2017-05-18 7:10 ` Thomas Petazzoni
2017-05-18 11:17 ` Baruch Siach
2017-05-18 11:24 ` Thomas Petazzoni
2017-05-18 11:37 ` Baruch Siach
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=20161116173605.12aa2e5b@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 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.