From: "Gao Feng" <gfree.wind@foxmail.com>
To: "'Florian Westphal'" <fw@strlen.de>, <gfree.wind@foxmail.com>
Cc: <pablo@netfilter.org>, <netfilter-devel@vger.kernel.org>
Subject: RE: [PATCH nf-next 1/1] netfilter: Remove useless variable timeouts in init_conntrack
Date: Thu, 6 Apr 2017 08:45:12 +0800 [thread overview]
Message-ID: <002001d2ae6f$0d6e48e0$284adaa0$@foxmail.com> (raw)
In-Reply-To: <20170405131728.GA15315@breakpoint.cc>
Hi Florian,
> -----Original Message-----
> From: Florian Westphal [mailto:fw@strlen.de]
> Sent: Wednesday, April 5, 2017 9:17 PM
> To: gfree.wind@foxmail.com
> Cc: pablo@netfilter.org; netfilter-devel@vger.kernel.org; Gao Feng
> <fgao@ikuai8.com>
> Subject: Re: [PATCH nf-next 1/1] netfilter: Remove useless variable
timeouts in
> init_conntrack
>
> gfree.wind@foxmail.com <gfree.wind@foxmail.com> wrote:
> > From: Gao Feng <fgao@ikuai8.com>
> >
> > All l4_proto->new callbacks don't use the param timeouts currently, so
> > remove it from param list. Then the variable timeouts isn't used as
> > right value in init_conntrack, so remove it too.
> > Signed-off-by: Gao Feng <fgao@ikuai8.com>
> > ---
> > include/net/netfilter/nf_conntrack_l4proto.h | 2 +-
> > net/ipv4/netfilter/nf_conntrack_proto_icmp.c | 2 +-
> > net/netfilter/nf_conntrack_core.c | 13 ++-----------
> > net/netfilter/nf_conntrack_proto_dccp.c | 2 +-
> > net/netfilter/nf_conntrack_proto_sctp.c | 2 +-
> > net/netfilter/nf_conntrack_proto_tcp.c | 2 +-
> > net/netfilter/nf_conntrack_proto_udp.c | 2 +-
> > 7 files changed, 8 insertions(+), 17 deletions(-)
>
> What about net/netfilter/nf_conntrack_proto_gre.c ?
It's my fault.
I only checked the protos in nf_conntrack_ipv4.h.
Best Regards
Feng
next prev parent reply other threads:[~2017-04-06 0:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 4:49 [PATCH nf-next 1/1] netfilter: Remove useless variable timeouts in init_conntrack gfree.wind
2017-04-05 13:17 ` Florian Westphal
2017-04-06 0:45 ` Gao Feng [this message]
2017-04-05 20:01 ` kbuild test robot
2017-04-06 0:46 ` Gao Feng
2017-04-05 20:58 ` kbuild test robot
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='002001d2ae6f$0d6e48e0$284adaa0$@foxmail.com' \
--to=gfree.wind@foxmail.com \
--cc=fw@strlen.de \
--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).