From: ogawa.yasufumi@lab.ntt.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 2/6] shared/sec: rename func for parsing comp name
Date: Tue, 21 May 2019 11:32:00 +0900 [thread overview]
Message-ID: <1558405924-8303-3-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <1558405924-8303-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp>
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
This update is to rename function `decode_component_name_value()` to
`parse_comp_name()` which is enough to describe the behaviour.
Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
src/shared/secondary/spp_worker_th/cmd_parser.c | 8 ++++----
src/shared/secondary/spp_worker_th/spp_proc.c | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/src/shared/secondary/spp_worker_th/cmd_parser.c b/src/shared/secondary/spp_worker_th/cmd_parser.c
index 6fc3a51..e99cdeb 100644
--- a/src/shared/secondary/spp_worker_th/cmd_parser.c
+++ b/src/shared/secondary/spp_worker_th/cmd_parser.c
@@ -325,10 +325,10 @@ parse_comp_action(void *output, const char *arg_val,
/* decoding procedure of action for component command */
static int
-decode_component_name_value(void *output, const char *arg_val,
- int allow_override __attribute__ ((unused)))
+parse_comp_name(void *output, const char *arg_val,
+ int allow_override __attribute__ ((unused)))
{
- int ret = SPP_RET_OK;
+ int ret;
struct sppwk_cmd_comp *component = output;
/* "stop" has no core ID parameter. */
@@ -802,7 +802,7 @@ cmd_ops_list[][SPPWK_MAX_PARAMS] = {
{
.name = "component name",
.offset = offsetof(struct spp_command, spec.comp),
- .func = decode_component_name_value
+ .func = parse_comp_name
},
{
.name = "core",
diff --git a/src/shared/secondary/spp_worker_th/spp_proc.c b/src/shared/secondary/spp_worker_th/spp_proc.c
index 53dd3f8..e552bf1 100644
--- a/src/shared/secondary/spp_worker_th/spp_proc.c
+++ b/src/shared/secondary/spp_worker_th/spp_proc.c
@@ -730,7 +730,7 @@ int
spp_get_component_id(const char *name)
{
struct spp_component_info *component_info =
- g_mng_data_addr.p_component_info;
+ g_mng_data_addr.p_component_info;
int cnt = 0;
if (name[0] == '\0')
--
2.17.1
next prev parent reply other threads:[~2019-05-21 2:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 2:31 [spp] [PATCH 0/6] Revise name of funcs for parsing actions ogawa.yasufumi
2019-05-21 2:31 ` [spp] [PATCH 1/6] shared/sec: rename parse comp action val ogawa.yasufumi
2019-05-21 2:32 ` ogawa.yasufumi [this message]
2019-05-21 2:32 ` [spp] [PATCH 3/6] shared/sec: refacotr comments for parse comp name ogawa.yasufumi
2019-05-21 2:32 ` [spp] [PATCH 4/6] shared/sec: rename func for parsing lcore ID ogawa.yasufumi
2019-05-21 2:32 ` [spp] [PATCH 5/6] shared/sec: rename func of parsing comp type ogawa.yasufumi
2019-05-21 2:32 ` [spp] [PATCH 6/6] shared/sec: rename parsing comp action ogawa.yasufumi
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=1558405924-8303-3-git-send-email-ogawa.yasufumi@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--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).