From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] iproute2: fix build with uclibc-ng
Date: Thu, 15 Feb 2018 09:59:51 +0100 [thread overview]
Message-ID: <20180215095951.3d3c5bac@windsurf.lan> (raw)
In-Reply-To: <4e9671e90351352197f0d14165365e811435633e.1518674314.git.baruch@tkos.co.il>
Hello,
On Thu, 15 Feb 2018 07:58:34 +0200, Baruch Siach wrote:
> ublibc-ng does not provide PF_VSOCK/AF_VSOCK definitions. Add them
> locally until ucblibc-ng updates its headers.
>
> Fixes:
> http://autobuild.buildroot.net/results/3d5/3d5a29e3c61ff071628c2937844ea4156059b3dd/
>
> Cc: Petr Vorel <petr.vorel@gmail.com>
> Cc: Waldemar Brodkorb <wbx@openadk.org>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Is this a fallout from:
65a7e82c891e967c4dd96678be72b8acf16a0127 iproute2: bump to version 4.15.0
i.e, is this patch for next, or master ? The autobuilder failure you
pointed is on the next branch, so I assume that this patch is for next,
but you didn't made it explicit.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-02-15 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 5:58 [Buildroot] [PATCH] iproute2: fix build with uclibc-ng Baruch Siach
2018-02-15 8:59 ` Thomas Petazzoni [this message]
2018-02-15 9:03 ` Baruch Siach
2018-02-15 9:54 ` 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=20180215095951.3d3c5bac@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