From: yasufum.o@gmail.com
To: spp@dpdk.org, ferruh.yigit@intel.com, yasufum.o@gmail.com
Subject: [spp] [PATCH] shared/sec: remove log_all_mng_info from header
Date: Thu, 25 Jul 2019 20:25:14 +0900 [thread overview]
Message-ID: <20190725112514.27266-1-yasufum.o@gmail.com> (raw)
From: Yasufumi Ogawa <yasufum.o@gmail.com>
log_all_mng_info() is for logging internal status and called only from
backup_mng_info(). It is no need to be defined in `cmd_utils.h`.
Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
---
src/shared/secondary/spp_worker_th/cmd_utils.c | 2 +-
src/shared/secondary/spp_worker_th/cmd_utils.h | 6 ------
2 files changed, 1 insertion(+), 7 deletions(-)
diff --git a/src/shared/secondary/spp_worker_th/cmd_utils.c b/src/shared/secondary/spp_worker_th/cmd_utils.c
index c879e9c..7f692e3 100644
--- a/src/shared/secondary/spp_worker_th/cmd_utils.c
+++ b/src/shared/secondary/spp_worker_th/cmd_utils.c
@@ -268,7 +268,7 @@ log_interface_info(const struct iface_info *iface_info)
}
/* Dump of all management information */
-void
+static void
log_all_mng_info(
const struct core_mng_info *core,
const struct sppwk_comp_info *component,
diff --git a/src/shared/secondary/spp_worker_th/cmd_utils.h b/src/shared/secondary/spp_worker_th/cmd_utils.h
index 0e67357..56f11ac 100644
--- a/src/shared/secondary/spp_worker_th/cmd_utils.h
+++ b/src/shared/secondary/spp_worker_th/cmd_utils.h
@@ -211,12 +211,6 @@ void log_component_info(const struct sppwk_comp_info *component_info);
/* Output log message for interface information */
void log_interface_info(const struct iface_info *iface_info);
-/* Output log message for all management information */
-void log_all_mng_info(
- const struct core_mng_info *core,
- const struct sppwk_comp_info *component,
- const struct iface_info *interface);
-
/* Copy management information */
void copy_mng_info(
struct core_mng_info *dst_core,
--
2.17.1
reply other threads:[~2019-07-25 11:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190725112514.27266-1-yasufum.o@gmail.com \
--to=yasufum.o@gmail.com \
--cc=ferruh.yigit@intel.com \
--cc=spp@dpdk.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).