From: Paul Bolle <pebolle@tiscali.nl>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Matteo Croce <technoboy85@gmail.com>,
Patrick McHardy <kaber@trash.net>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
"David S. Miller" <davem@davemloft.net>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org
Subject: netfilter: NETFILTER_XT_NAT?
Date: Wed, 03 Sep 2014 22:17:24 +0200 [thread overview]
Message-ID: <1409775444.5546.47.camel@x220> (raw)
Hi Pablo,
Your commit 8993cf8edf42 ("netfilter: move NAT Kconfig switches out of
the iptables scope") just landed in linux-next (ie, in next-20140903).
It claims to add NETFILTER_XT_NAT.
That commit does add two select statements for NETFILTER_XT_NAT, and a
Makefile line checking for NETFILTER_XT_NAT. But it does not add the
actual Kconfig symbol NETFILTER_XT_NAT. This is a bit confusing. Do you
know what may have happened here?
Paul Bolle
reply other threads:[~2014-09-03 20:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1409775444.5546.47.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=technoboy85@gmail.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).