From: Stephen Hemminger <stephen@networkplumber.org>
To: Loganaden Velvindron <logan@hackers.mu>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] iproute2: Fix musl compatibility
Date: Wed, 2 Mar 2016 11:03:40 -0800 [thread overview]
Message-ID: <20160302110340.0d73e5ee@xeon-e3> (raw)
In-Reply-To: <20160222113447.GA10262@mx.elandsys.com>
On Mon, 22 Feb 2016 03:34:48 -0800
Loganaden Velvindron <logan@hackers.mu> wrote:
> diff --git a/include/linux/netfilter.h b/include/linux/netfilter.h
> index b71b4c9..3e4e6ae 100644
> --- a/include/linux/netfilter.h
> +++ b/include/linux/netfilter.h
> @@ -4,8 +4,6 @@
> #include <linux/types.h>
>
> #include <linux/sysctl.h>
> -#include <linux/in.h>
> -#include <linux/in6.h>
>
> /* Responses from hook functio
Sorry, I have to reject this.
All include files in include/linux come from headers automatically generated from upstream
Linux source. This is the only way to ensure long term ABI/API consistency
with kernel.
Either fix musl or submit patches to upstream kernel and get them merged.
prev parent reply other threads:[~2016-03-02 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 11:34 [PATCH] iproute2: Fix musl compatibility Loganaden Velvindron
2016-03-02 18:11 ` Loganaden Velvindron
2016-03-02 19:01 ` Stephen Hemminger
2016-03-02 19:03 ` Stephen Hemminger [this message]
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=20160302110340.0d73e5ee@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=logan@hackers.mu \
--cc=netdev@vger.kernel.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 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.