From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Pablo Neira Ayuso <pablo@netfilter.org>,
NetFilter <netfilter-devel@vger.kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jeremy Sowden <jeremy@azazel.net>
Subject: linux-next: build warnings after merge of the netfilter-next tree
Date: Wed, 14 Aug 2019 12:01:10 +1000 [thread overview]
Message-ID: <20190814120110.3c17ddec@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
Hi all,
After merging the netfilter-next tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:
In file included from <command-line>:
include/uapi/linux/netfilter_ipv6/ip6t_LOG.h:5:2: warning: #warning "Please update iptables, this file will be removed soon!" [-Wcpp]
#warning "Please update iptables, this file will be removed soon!"
^~~~~~~
In file included from <command-line>:
include/uapi/linux/netfilter_ipv4/ipt_LOG.h:5:2: warning: #warning "Please update iptables, this file will be removed soon!" [-Wcpp]
#warning "Please update iptables, this file will be removed soon!"
^~~~~~~
Introduced by commit
2a475c409fe8 ("kbuild: remove all netfilter headers from header-test blacklist.")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-08-14 2:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 2:01 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-05 1:19 linux-next: build warnings after merge of the netfilter-next tree Stephen Rothwell
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=20190814120110.3c17ddec@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jeremy@azazel.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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;
as well as URLs for NNTP newsgroup(s).