From: yasufum.o@gmail.com
To: spp@dpdk.org, ferruh.yigit@intel.com, yasufum.o@gmail.com
Subject: [spp] [PATCH 2/2] spp_pcap: change name of struct cmd_response
Date: Mon, 24 Jun 2019 16:10:51 +0900 [thread overview]
Message-ID: <20190624071051.23342-3-yasufum.o@gmail.com> (raw)
In-Reply-To: <20190624071051.23342-1-yasufum.o@gmail.com>
From: Yasufumi Ogawa <yasufum.o@gmail.com>
This update is to rename struct `cmd_response` to
`cmd_res_formatter_ops` because it is a set of tag and operation
function for parsing command.
Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
---
src/pcap/cmd_runner.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/src/pcap/cmd_runner.c b/src/pcap/cmd_runner.c
index 55f15bf..4a74af2 100644
--- a/src/pcap/cmd_runner.c
+++ b/src/pcap/cmd_runner.c
@@ -47,7 +47,7 @@ struct cmd_result {
/* command response list control structure */
/* TODO(yasufum) merge it to the same definition in shared/.../cmd_runner.c */
-struct cmd_response {
+struct cmd_res_formatter_ops {
char tag_name[SPPWK_NAME_BUFSZ]; /* JSON Tag name */
int (*func)(const char *name, char **output, void *tmp);
};
@@ -548,7 +548,7 @@ append_core_value(const char *name, char **output,
/* append string of command response list for JSON format */
static int
append_response_list_value(char **output,
- struct cmd_response *list,
+ struct cmd_res_formatter_ops *list,
void *tmp)
{
int ret = SPPWK_RET_NG;
@@ -607,14 +607,14 @@ append_response_list_value(char **output,
#define COMMAND_RESP_TAG_LIST_EMPTY { "", NULL }
/* command response result string list */
-struct cmd_response response_result_list[] = {
+struct cmd_res_formatter_ops response_result_list[] = {
{ "result", append_result_value },
{ "error_details", append_error_details_value },
COMMAND_RESP_TAG_LIST_EMPTY
};
/* command response status information string list */
-struct cmd_response response_info_list[] = {
+struct cmd_res_formatter_ops response_info_list[] = {
{ "client-id", append_client_id_value },
{ "status", append_capture_status_value },
{ "master-lcore", append_master_lcore_value },
--
2.17.1
prev parent reply other threads:[~2019-06-24 7:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 7:10 [spp] [PATCH 0/2] Rename " yasufum.o
2019-06-24 7:10 ` [spp] [PATCH 1/2] shared/sec: change name of " yasufum.o
2019-06-24 7:10 ` yasufum.o [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=20190624071051.23342-3-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).