From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Davide Caratti <dcaratti@redhat.com>
Cc: Patrick McHardy <kaber@trash.net>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
"David S. Miller" <davem@davemloft.net>,
Arturo Borrero Gonzalez <arturo@debian.org>,
Florian Westphal <fw@strlen.de>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org
Subject: Re: [PATCH nf-next 1/3] netfilter: built-in NAT support for DCCP
Date: Thu, 20 Oct 2016 14:37:26 +0200 [thread overview]
Message-ID: <20161020123726.GA10040@salvia> (raw)
In-Reply-To: <96409ea5aa35dd371f7ad0efa622339f82318b24.1476956422.git.dcaratti@redhat.com>
On Thu, Oct 20, 2016 at 12:26:23PM +0200, Davide Caratti wrote:
> CONFIG_NF_NAT_PROTO_DCCP is no more a tristate. When set to y, NAT
> support for DCCP protocol is built-in into nf_nat.ko.
>
> Signed-off-by: Davide Caratti <dcaratti@redhat.com>
> ---
> include/net/netfilter/nf_nat_l4proto.h | 3 +++
> net/netfilter/Kconfig | 2 +-
> net/netfilter/Makefile | 3 ++-
> net/netfilter/nf_nat_core.c | 4 ++++
> net/netfilter/nf_nat_proto_dccp.c | 36 +---------------------------------
> 5 files changed, 11 insertions(+), 37 deletions(-)
>
> diff --git a/include/net/netfilter/nf_nat_l4proto.h b/include/net/netfilter/nf_nat_l4proto.h
> index 12f4cc8..6328c18 100644
> --- a/include/net/netfilter/nf_nat_l4proto.h
> +++ b/include/net/netfilter/nf_nat_l4proto.h
> @@ -54,6 +54,9 @@ extern const struct nf_nat_l4proto nf_nat_l4proto_udp;
> extern const struct nf_nat_l4proto nf_nat_l4proto_icmp;
> extern const struct nf_nat_l4proto nf_nat_l4proto_icmpv6;
> extern const struct nf_nat_l4proto nf_nat_l4proto_unknown;
> +#if IS_ENABLED(CONFIG_NF_NAT_PROTO_DCCP)
I think you can replace this by:
#ifdef CONFIG_NF_NAT_PROTO_DCCP
given that IS_ENABLED catches the module case too.
This is is just a code readability nitpick, so whoever reads this code
understands that we have no module support for this anymore.
next prev parent reply other threads:[~2016-10-20 12:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 10:26 [PATCH nf-next 0/3] netfilter: built-in NAT support for DCCP, SCTP, UDPlite Davide Caratti
2016-10-20 10:26 ` [PATCH nf-next 1/3] netfilter: built-in NAT support for DCCP Davide Caratti
2016-10-20 12:37 ` Pablo Neira Ayuso [this message]
2016-10-20 16:30 ` Davide Caratti
2016-10-20 10:26 ` [PATCH nf-next 2/3] netfilter: built-in NAT support for SCTP Davide Caratti
2016-10-20 10:26 ` [PATCH nf-next 3/3] netfilter: built-in NAT support for UDPlite Davide Caratti
2016-10-20 10:28 ` [PATCH nf-next 0/3] netfilter: built-in NAT support for DCCP, SCTP, UDPlite Florian Westphal
2016-10-20 10:36 ` Davide Caratti
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=20161020123726.GA10040@salvia \
--to=pablo@netfilter.org \
--cc=arturo@debian.org \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=fw@strlen.de \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox