From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH iproute2 0/7] localize functions where possible
Date: Thu, 1 Jun 2023 10:21:38 -0700 [thread overview]
Message-ID: <20230601172145.51357-1-stephen@networkplumber.org> (raw)
This is the result of using a script to examine where functions
are defined in one file but not used in any other file.
Found some dead code in process.
Stephen Hemminger (7):
utils: make local cmdline functions static
libnetlink: drop unused rtnl_talk_iov
bridge: make print_vlan_info static
rt_names: drop unused rtnl_addrprot_a2n
ip: make print_rta_gateway static
xfrm: make xfrm_stat_print_nokeys static
rdma: make rd_attr_check static
bridge/br_common.h | 1 -
bridge/vlan.c | 3 ++-
include/libnetlink.h | 3 ---
include/rt_names.h | 1 -
include/utils.h | 3 ---
ip/ip_common.h | 2 --
ip/iproute.c | 2 +-
ip/xfrm.h | 1 -
ip/xfrm_state.c | 2 +-
lib/libnetlink.c | 6 ------
lib/rt_names.c | 33 ---------------------------------
lib/utils.c | 6 +++---
rdma/rdma.h | 1 -
rdma/utils.c | 2 +-
14 files changed, 8 insertions(+), 58 deletions(-)
--
2.39.2
next reply other threads:[~2023-06-01 17:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 17:21 Stephen Hemminger [this message]
2023-06-01 17:21 ` [PATCH iproute2 1/7] utils: make local cmdline functions static Stephen Hemminger
2023-06-01 17:21 ` [PATCH iproute2 2/7] libnetlink: drop unused rtnl_talk_iov Stephen Hemminger
2023-06-01 17:21 ` [PATCH iproute2 3/7] bridge: make print_vlan_info static Stephen Hemminger
2023-06-01 17:25 ` Nikolay Aleksandrov
2023-06-01 17:21 ` [PATCH iproute2 4/7] rt_names: drop unused rtnl_addrprot_a2n Stephen Hemminger
2023-06-01 17:21 ` [PATCH iproute2 5/7] ip: make print_rta_gateway static Stephen Hemminger
2023-06-01 17:21 ` [PATCH iproute2 6/7] xfrm: make xfrm_stat_print_nokeys static Stephen Hemminger
2023-06-01 17:21 ` [PATCH iproute2 7/7] rdma: make rd_attr_check static Stephen Hemminger
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=20230601172145.51357-1-stephen@networkplumber.org \
--to=stephen@networkplumber.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).