From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] trinity: fix glibc/kernel headers conflict
Date: Thu, 13 Apr 2017 21:29:19 +0200 [thread overview]
Message-ID: <20170413212919.3382430b@free-electrons.com> (raw)
In-Reply-To: <0c3077fb3a4c82ea2570106a3357e9cae19cdd3d.1492060046.git.baruch@tkos.co.il>
Hello,
On Thu, 13 Apr 2017 08:07:26 +0300, Baruch Siach wrote:
> Add upstream patch that fixes conflicting definitions of ax25 related structs.
>
> Fixes:
> http://autobuild.buildroot.net/results/b40/b40d045f41dc4dbc66d5092ea5e9e045cd825e31/
> http://autobuild.buildroot.net/results/367/367199b6071c450159aa2ea74d6d1b4b7cb89a88/
> http://autobuild.buildroot.net/results/35e/35e97e51a6f7184d7b708c62a726ab91a0f546b2/
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> package/trinity/trinity.hash | 1 +
> package/trinity/trinity.mk | 2 ++
> 2 files changed, 3 insertions(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-04-13 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 5:07 [Buildroot] [PATCH] trinity: fix glibc/kernel headers conflict Baruch Siach
2017-04-13 19:29 ` Thomas Petazzoni [this message]
2017-04-24 19:24 ` 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=20170413212919.3382430b@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