From: ogawa.yasufumi@lab.ntt.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 0/9] Refactor func and struct for spp_pcap resources
Date: Fri, 31 May 2019 17:51:30 +0900 [thread overview]
Message-ID: <1559292699-26940-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
This series of patches is to refactor functions, structs and vars for
manipulating resources of spp_pcap.
Yasufumi Ogawa (9):
spp_pcap: rename enum spp_core_status
spp_pcap: rename file of util libs
spp_pcap: refactor parse error code
spp_pcap: rename define starts from SPP_CMD_MAX
spp_pcap: rename define of buffer size for cmds
spp_pcap: revise name of error message object
spp_pcap: revise return codes
spp_pcap: rename struct spp_port_info
spp_pcap: rename struct spp_port_index
src/pcap/Makefile | 2 +-
src/pcap/{command_dec.c => cmd_parser.c} | 72 +++--
src/pcap/{command_dec.h => cmd_parser.h} | 44 +--
src/pcap/{command_proc.c => cmd_runner.c} | 304 +++++++++---------
src/pcap/{command_proc.h => cmd_runner.h} | 14 +-
src/pcap/cmd_utils.c | 62 ++--
src/pcap/cmd_utils.h | 90 +++---
src/pcap/spp_pcap.c | 193 +++++------
src/pcap/spp_pcap.h | 4 +-
.../secondary/spp_worker_th/cmd_utils.h | 2 +-
10 files changed, 398 insertions(+), 389 deletions(-)
rename src/pcap/{command_dec.c => cmd_parser.c} (68%)
rename src/pcap/{command_dec.h => cmd_parser.h} (69%)
rename src/pcap/{command_proc.c => cmd_runner.c} (81%)
rename src/pcap/{command_proc.h => cmd_runner.h} (71%)
--
2.17.1
next reply other threads:[~2019-05-31 8:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 8:51 ogawa.yasufumi [this message]
2019-05-31 8:51 ` [spp] [PATCH 1/9] spp_pcap: rename enum spp_core_status ogawa.yasufumi
2019-05-31 8:51 ` [spp] [PATCH 2/9] spp_pcap: rename file of util libs ogawa.yasufumi
2019-05-31 8:51 ` [spp] [PATCH 3/9] spp_pcap: refactor parse error code ogawa.yasufumi
2019-05-31 8:51 ` [spp] [PATCH 4/9] spp_pcap: rename define starts from SPP_CMD_MAX ogawa.yasufumi
2019-05-31 8:51 ` [spp] [PATCH 5/9] spp_pcap: rename define of buffer size for cmds ogawa.yasufumi
2019-05-31 8:51 ` [spp] [PATCH 6/9] spp_pcap: revise name of error message object ogawa.yasufumi
2019-05-31 8:51 ` [spp] [PATCH 7/9] spp_pcap: revise return codes ogawa.yasufumi
2019-05-31 8:51 ` [spp] [PATCH 8/9] spp_pcap: rename struct spp_port_info ogawa.yasufumi
2019-05-31 8:51 ` [spp] [PATCH 9/9] spp_pcap: rename struct spp_port_index 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=1559292699-26940-1-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).