From: Patrick McHardy <kaber@trash.net>
To: Adrian Bunk <bunk@stusta.de>
Cc: coreteam@netfilter.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [netfilter-core] [2.6 patch] net/*/nf_conntrack_*.c:possible cleanups
Date: Sat, 02 Dec 2006 00:34:22 +0100 [thread overview]
Message-ID: <4570BBFE.8090209@trash.net> (raw)
In-Reply-To: <20061201210113.GI11084@stusta.de>
Adrian Bunk wrote:
> This patch contains the following possible cleanups:
> - make the following needlessly global functions static:
> - net/netfilter/nf_conntrack_core.c: nf_conntrack_register_cache()
> - net/netfilter/nf_conntrack_core.c: nf_conntrack_unregister_cache()
> - net/netfilter/nf_conntrack_core.c: __nf_conntrack_attach()
> - net/netfilter/nf_conntrack_core.c: set_hashsize()
> - net/netfilter/nf_conntrack_proto_sctp.c: nf_conntrack_proto_sctp_init()
> - net/netfilter/nf_conntrack_proto_sctp.c: nf_conntrack_proto_sctp_fini()
> - make the following needlessly global variables/locks/structs static:
> - net/ipv6/netfilter/nf_conntrack_reasm.c: nf_ct_frag6_secret_interval
> - net/ipv6/netfilter/nf_conntrack_reasm.c: nf_ct_frag6_mem
> - net/netfilter/nf_conntrack_core.c: nf_ct_cache_lock
> - net/netfilter/nf_conntrack_proto_sctp.c: nf_conntrack_protocol_sctp4
> - net/netfilter/nf_conntrack_proto_sctp.c: nf_conntrack_protocol_sctp6
> - #if 0 the following unused global functions:
> - net/ipv6/netfilter/nf_conntrack_reasm.c: nf_ct_frag6_kfree_frags()
> - net/netfilter/nf_conntrack_core.c: nf_conntrack_tuple_taken()
> - net/netfilter/nf_conntrack_core.c: nf_ct_invert_tuplepr()
> - remove the following unused or write-only variables:
> - net/ipv4/netfilter/nf_conntrack_l3proto_ipv4.c: nat_module_is_loaded
> - net/ipv6/netfilter/nf_conntrack_reasm.c: nf_ct_frag6_nqueues
> - remove the following unused hooks:
> - net/netfilter/nf_conntrack_core.c: nf_conntrack_destroyed()
> - net/netfilter/nf_conntrack_ftp.c: nf_nat_ftp_hook()
> - remove the following unused EXPORT_SYMBOL's:
> - nf_ct_iterate_cleanup
> - nf_ct_protos
> - nf_ct_l3protos
>
> Please review which of these changes make sense and which might conflict
> with pending patches.
Thanks Adrian. We have a large nf_conntrack merge coming up, which
conflicts with this patch and includes new users of some of these
symbols. Please send your patch again once these changes have
been merged.
prev parent reply other threads:[~2006-12-01 23:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 21:01 [2.6 patch] net/*/nf_conntrack_*.c:possible cleanups Adrian Bunk
2006-12-01 23:34 ` Patrick McHardy [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=4570BBFE.8090209@trash.net \
--to=kaber@trash.net \
--cc=bunk@stusta.de \
--cc=coreteam@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).