From: <jackie.huang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] net-tools: fix building with linux-4.8
Date: Sun, 9 Oct 2016 08:56:05 +0800 [thread overview]
Message-ID: <cover.1475973333.git.jackie.huang@windriver.com> (raw)
From: Jackie Huang <jackie.huang@windriver.com>
This is a follow-up from the thread:
https://patchwork.openembedded.org/patch/132637/
I reverted Bruce's change and picked Randy's fix for net-tools,
build tests are fine for qemux86-64/ppc/arm/arm64/mips and I
booted core-image-full-cmdline for qemuarm64 and checked that
iptunnel works fine.
--
The following changes since commit ac647ea6964e166c395334fe107015030adc1b76:
update-rc.d.bbclass: check that init script is executable before running it (2016-10-07 16:53:18 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib.git jhuang0/d_net-tools-linux-4.8_161008-1
http://git.pokylinux.org/cgit.cgi//log/?h=jhuang0/d_net-tools-linux-4.8_161008-1
Jackie Huang (2):
Revert "linux-libc-headers: if_tunnel: remove include of if/ip/in6.h"
net-tools: fix building with linux-4.8
.../net-tools-fix-building-with-linux-4.8.patch | 52 ++++++++++++++++++++++
.../net-tools/net-tools_1.60-26.bb | 1 +
...1-if_tunnel-remove-include-of-if-ip-in6.h.patch | 33 --------------
.../linux-libc-headers/linux-libc-headers_4.8.bb | 1 -
4 files changed, 53 insertions(+), 34 deletions(-)
create mode 100644 meta/recipes-extended/net-tools/net-tools/net-tools-fix-building-with-linux-4.8.patch
delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers/0001-if_tunnel-remove-include-of-if-ip-in6.h.patch
--
2.8.3
next reply other threads:[~2016-10-09 1:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 0:56 jackie.huang [this message]
2016-10-09 0:56 ` [PATCH 1/2] Revert "linux-libc-headers: if_tunnel: remove include of if/ip/in6.h" jackie.huang
2016-10-09 0:56 ` [PATCH 2/2] net-tools: fix building with linux-4.8 jackie.huang
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=cover.1475973333.git.jackie.huang@windriver.com \
--to=jackie.huang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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