From: Felix Janda <felix.janda@posteo.de>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 1/2] Avoid in6_addr redefinition
Date: Sun, 3 Jan 2016 21:10:28 +0100 [thread overview]
Message-ID: <20160103201028.GA4210@nyan> (raw)
On 2015-11-19 22:32:50 GMT Stephen Hemminger <stephen@networkplumber.org> wrote:
> This header file comes from iptables. Please fix there, otherwise
> on next time someone does merge from there it will break.
It is already fixed in iptables:
https://git.netfilter.org/iptables/commit/include/libiptc/ipt_kernel_headers.h?id=0bb1859e2d6dd79a0a59c3ee65f6a78cba118b86
Please sync the header with iptables.
Felix
next reply other threads:[~2016-01-03 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-03 20:10 Felix Janda [this message]
2016-01-03 23:16 ` [PATCH iproute2 1/2] Avoid in6_addr redefinition Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2015-11-19 21:05 [PATCH iproute2 0/2] Build fixes for the musl C library Thomas Petazzoni
2015-11-19 21:05 ` [PATCH iproute2 1/2] Avoid in6_addr redefinition Thomas Petazzoni
2015-11-19 22:32 ` Stephen Hemminger
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=20160103201028.GA4210@nyan \
--to=felix.janda@posteo.de \
--cc=20151119143250.44a24eb4@xeon-e3 \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=thomas.petazzoni@free-electrons.com \
/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;
as well as URLs for NNTP newsgroup(s).