From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: dead CONFIG_ variables: net/ipv4/
Date: Wed, 2 May 2007 17:15:01 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705021711450.16967@localhost.localdomain> (raw)
again, this list contains some CONFIG_ variables that aren't
technically dead, but *really* should be renamed to not be confused
with Kconfig variables. there are, however, legitimately dead ones in
the following in places:
$ ../dead_config.sh net/ipv4
========== IP_FIB_TRIE_STATS ==========
net/ipv4/fib_trie.c:#undef CONFIG_IP_FIB_TRIE_STATS
net/ipv4/fib_trie.c:#ifdef CONFIG_IP_FIB_TRIE_STATS
net/ipv4/fib_trie.c:#ifdef CONFIG_IP_FIB_TRIE_STATS
net/ipv4/fib_trie.c:#ifdef CONFIG_IP_FIB_TRIE_STATS
net/ipv4/fib_trie.c:#ifdef CONFIG_IP_FIB_TRIE_STATS
net/ipv4/fib_trie.c:#ifdef CONFIG_IP_FIB_TRIE_STATS
net/ipv4/fib_trie.c:#ifdef CONFIG_IP_FIB_TRIE_STATS
net/ipv4/fib_trie.c:#ifdef CONFIG_IP_FIB_TRIE_STATS
net/ipv4/fib_trie.c:#ifdef CONFIG_IP_FIB_TRIE_STATS
net/ipv4/fib_trie.c:#ifdef CONFIG_IP_FIB_TRIE_STATS
net/ipv4/fib_trie.c:#ifdef CONFIG_IP_FIB_TRIE_STATS
net/ipv4/fib_trie.c:#ifdef CONFIG_IP_FIB_TRIE_STATS
net/ipv4/fib_trie.c:#endif /* CONFIG_IP_FIB_TRIE_STATS */
========== IP_NF_NAT ==========
net/ipv4/netfilter/Kconfig:# If they want FTP, set to $CONFIG_IP_NF_NAT (m or y),
net/ipv4/netfilter/nf_conntrack_l3proto_ipv4.c:#if !defined(CONFIG_IP_NF_NAT) && !defined(CONFIG_IP_NF_NAT_MODULE)
net/ipv4/netfilter/nf_conntrack_l3proto_ipv4.c:#if !defined(CONFIG_IP_NF_NAT) && !defined(CONFIG_IP_NF_NAT_MODULE)
========== IP_NOSIOCRT ==========
net/ipv4/fib_frontend.c:#ifndef CONFIG_IP_NOSIOCRT
========== IP_PIMSM ==========
net/ipv4/ipmr.c:#define CONFIG_IP_PIMSM 1
net/ipv4/ipmr.c:#ifdef CONFIG_IP_PIMSM
net/ipv4/ipmr.c:#ifdef CONFIG_IP_PIMSM
net/ipv4/ipmr.c:#ifdef CONFIG_IP_PIMSM
net/ipv4/ipmr.c:#ifdef CONFIG_IP_PIMSM
net/ipv4/ipmr.c:#ifdef CONFIG_IP_PIMSM
net/ipv4/ipmr.c:#ifdef CONFIG_IP_PIMSM
net/ipv4/ipmr.c:#ifdef CONFIG_IP_PIMSM
net/ipv4/ipmr.c:#ifdef CONFIG_IP_PIMSM
net/ipv4/ipmr.c:#ifdef CONFIG_IP_PIMSM
net/ipv4/ipmr.c:#ifdef CONFIG_IP_PIMSM
========== IP_ROUTE_PERVASIVE ==========
net/ipv4/fib_semantics.c:#ifdef CONFIG_IP_ROUTE_PERVASIVE
========== IP_VS_DH_TAB_BITS ==========
net/ipv4/ipvs/ip_vs_dh.c:#ifndef CONFIG_IP_VS_DH_TAB_BITS
net/ipv4/ipvs/ip_vs_dh.c:#define CONFIG_IP_VS_DH_TAB_BITS 8
net/ipv4/ipvs/ip_vs_dh.c:#define IP_VS_DH_TAB_BITS CONFIG_IP_VS_DH_TAB_BITS
net/ipv4/ipvs/ip_vs_dh.c:#define IP_VS_DH_TAB_BITS CONFIG_IP_VS_DH_TAB_BITS
net/ipv4/ipvs/ip_vs_dh.c:#define IP_VS_DH_TAB_SIZE (1 << IP_VS_DH_TAB_BITS)
========== IP_VS_LBLCR_DEBUG ==========
net/ipv4/ipvs/ip_vs_lblcr.c:#ifdef CONFIG_IP_VS_LBLCR_DEBUG
net/ipv4/ipvs/ip_vs_lblcr.c:#ifdef CONFIG_IP_VS_LBLCR_DEBUG
net/ipv4/ipvs/ip_vs_lblcr.c:#ifdef CONFIG_IP_VS_LBLCR_DEBUG
net/ipv4/ipvs/ip_vs_lblcr.c:#ifdef CONFIG_IP_VS_LBLCR_DEBUG
========== IP_VS_LBLCR_TAB_BITS ==========
net/ipv4/ipvs/ip_vs_lblcr.c:#ifndef CONFIG_IP_VS_LBLCR_TAB_BITS
net/ipv4/ipvs/ip_vs_lblcr.c:#define CONFIG_IP_VS_LBLCR_TAB_BITS 10
net/ipv4/ipvs/ip_vs_lblcr.c:#define IP_VS_LBLCR_TAB_BITS CONFIG_IP_VS_LBLCR_TAB_BITS
net/ipv4/ipvs/ip_vs_lblcr.c:#define IP_VS_LBLCR_TAB_BITS CONFIG_IP_VS_LBLCR_TAB_BITS
net/ipv4/ipvs/ip_vs_lblcr.c:#define IP_VS_LBLCR_TAB_SIZE (1 << IP_VS_LBLCR_TAB_BITS)
========== IP_VS_LBLC_TAB_BITS ==========
net/ipv4/ipvs/ip_vs_lblc.c:#ifndef CONFIG_IP_VS_LBLC_TAB_BITS
net/ipv4/ipvs/ip_vs_lblc.c:#define CONFIG_IP_VS_LBLC_TAB_BITS 10
net/ipv4/ipvs/ip_vs_lblc.c:#define IP_VS_LBLC_TAB_BITS CONFIG_IP_VS_LBLC_TAB_BITS
net/ipv4/ipvs/ip_vs_lblc.c:#define IP_VS_LBLC_TAB_BITS CONFIG_IP_VS_LBLC_TAB_BITS
net/ipv4/ipvs/ip_vs_lblc.c:#define IP_VS_LBLC_TAB_SIZE (1 << IP_VS_LBLC_TAB_BITS)
========== IP_VS_SH_TAB_BITS ==========
net/ipv4/ipvs/ip_vs_sh.c:#ifndef CONFIG_IP_VS_SH_TAB_BITS
net/ipv4/ipvs/ip_vs_sh.c:#define CONFIG_IP_VS_SH_TAB_BITS 8
net/ipv4/ipvs/ip_vs_sh.c:#define IP_VS_SH_TAB_BITS CONFIG_IP_VS_SH_TAB_BITS
net/ipv4/ipvs/ip_vs_sh.c:#define IP_VS_SH_TAB_BITS CONFIG_IP_VS_SH_TAB_BITS
net/ipv4/ipvs/ip_vs_sh.c:#define IP_VS_SH_TAB_SIZE (1 << IP_VS_SH_TAB_BITS)
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
next reply other threads:[~2007-05-02 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 21:15 Robert P. J. Day [this message]
2007-05-03 3:23 ` Patrick McHardy
2007-05-29 20:10 ` David Miller
2007-05-29 20:14 ` Robert P. J. Day
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=Pine.LNX.4.64.0705021711450.16967@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®