From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] musl: add more kernel headers guards
Date: Wed, 14 Feb 2018 22:02:37 +0100 [thread overview]
Message-ID: <20180214220237.379a45a5@windsurf.lan> (raw)
In-Reply-To: <00926ed70cd14972bac0ce653b1f383b4a31492c.1518524870.git.baruch@tkos.co.il>
Hello,
On Tue, 13 Feb 2018 14:27:49 +0200, Baruch Siach wrote:
> Kernel version 4.15 (not 4.16 as the musl commit log claims) allows
> disabling of more parts of the kernel headers definitions. Add upstream
> musl patch that defines the relevant macros. This solves issues of
> networking related symbols redefinition in kernel headers that cause
> headers conflicts. With that in place a subsequent commit will limit the
> musl/kernel headers conflict avoidance workaround in Buildroot to kernel
> headers older than 4.15. This workaround has been introduced in commit
> 196932cd91 (toolchain: workaround musl/kernel headers conflict).
>
> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> ...nal-uapi-guards-for-Linux-kernel-header-f.patch | 69 ++++++++++++++++++++++
> 1 file changed, 69 insertions(+)
> create mode 100644 package/musl/0002-add-additional-uapi-guards-for-Linux-kernel-header-f.patch
Both applied to next. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-02-14 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 12:27 [Buildroot] [PATCH 1/2] musl: add more kernel headers guards Baruch Siach
2018-02-13 12:27 ` [Buildroot] [PATCH 2/2] toolchain: limit musl/kernel headers conflict workaround Baruch Siach
2018-03-30 19:19 ` Peter Korsgaard
2018-02-13 12:32 ` [Buildroot] [PATCH 1/2] musl: add more kernel headers guards Thomas Petazzoni
2018-02-13 12:47 ` Baruch Siach
2018-02-14 21:02 ` Thomas Petazzoni [this message]
2018-03-30 19:19 ` Peter Korsgaard
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=20180214220237.379a45a5@windsurf.lan \
--to=thomas.petazzoni@bootlin.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