From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [libnftables PATCH 1/2] tests: fix deprecation warning xt_LOG
Date: Sat, 30 Nov 2013 22:32:30 +0100 [thread overview]
Message-ID: <20131130213230.GB25362@localhost> (raw)
In-Reply-To: <20131128113010.11152.61271.stgit@nfdev.cica.es>
On Thu, Nov 28, 2013 at 12:30:10PM +0100, Arturo Borrero Gonzalez wrote:
> This fix the warning:
>
> In file included from nft-expr_target-test.c:19:0:
> /usr/include/linux/netfilter_ipv4/ipt_LOG.h:4:2: warning:
> #warning "Please update iptables, this file will be removed soon!" [-Wcpp]
Applied. I have also included a copy of xt_LOG.h to avoid breaking the
compilation of the library if that header is missing in the system.
It's not installed and it's just a few extra bytes in the tree.
BTW, I remember that Eric asked to remove the compat part (LOG and
iprange) that is included in the nft-rule-add example some time ago.
Back then, we had no automated tests and it was providing a simple way
to make sure that xtables compat stuff was still working over
nftables. Now, I think it's better if we just include native nftables
instructions there not to get people confused.
Would you rework the nft-rule-add.c to add a simple nftables rule
using native instructions?
Thanks.
prev parent reply other threads:[~2013-11-30 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 11:30 [libnftables PATCH 1/2] tests: fix deprecation warning xt_LOG Arturo Borrero Gonzalez
2013-11-28 11:30 ` [libnftables PATCH 2/2] tests: extend test-script to also tests parsing Arturo Borrero Gonzalez
2013-11-30 21:07 ` Pablo Neira Ayuso
2013-11-30 21:32 ` Pablo Neira Ayuso [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=20131130213230.GB25362@localhost \
--to=pablo@netfilter.org \
--cc=arturo.borrero.glez@gmail.com \
--cc=netfilter-devel@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.