From: ogawa.yasufumi@lab.ntt.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 00/10] Refactor cmd parser in spp_pcap
Date: Fri, 31 May 2019 17:52:32 +0900 [thread overview]
Message-ID: <1559292762-27042-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 revise a set of functions, structs and vars
to be appropriately because Some of them are too redundant or vague in
meaning.
Yasufumi Ogawa (10):
spp_pcap: rename enum spp_command_type
spp_pcap: rename struct spp_command
spp_pcap: revise command response codes
spp_pcap: revise parser functions
spp_pcap: refactor func for splitting cmd tokens
spp_pcap: revise log msgs in parser func
spp_pcap: remove unused string list
spp_pcap: refactor comments of spp_pcap
spp_pcap: rename spp_get_core_status
spp_pcap: revise name of vars for parser error
src/pcap/cmd_parser.c | 158 ++++++++++--------
src/pcap/cmd_parser.h | 32 ++--
src/pcap/cmd_runner.c | 142 +++++++---------
src/pcap/cmd_utils.c | 4 +-
src/pcap/cmd_utils.h | 28 ++--
src/pcap/spp_pcap.c | 95 +++++------
src/pcap/spp_pcap.h | 12 +-
.../secondary/spp_worker_th/cmd_parser.c | 4 +-
.../secondary/spp_worker_th/cmd_parser.h | 3 +-
.../secondary/spp_worker_th/cmd_runner.c | 8 +-
10 files changed, 221 insertions(+), 265 deletions(-)
--
2.17.1
next reply other threads:[~2019-05-31 8:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 8:52 ogawa.yasufumi [this message]
2019-05-31 8:52 ` [spp] [PATCH 01/10] spp_pcap: rename enum spp_command_type ogawa.yasufumi
2019-05-31 8:52 ` [spp] [PATCH 02/10] spp_pcap: rename struct spp_command ogawa.yasufumi
2019-05-31 8:52 ` [spp] [PATCH 03/10] spp_pcap: revise command response codes ogawa.yasufumi
2019-05-31 8:52 ` [spp] [PATCH 04/10] spp_pcap: revise parser functions ogawa.yasufumi
2019-05-31 8:52 ` [spp] [PATCH 05/10] spp_pcap: refactor func for splitting cmd tokens ogawa.yasufumi
2019-05-31 8:52 ` [spp] [PATCH 06/10] spp_pcap: revise log msgs in parser func ogawa.yasufumi
2019-05-31 8:52 ` [spp] [PATCH 07/10] spp_pcap: remove unused string list ogawa.yasufumi
2019-05-31 8:52 ` [spp] [PATCH 08/10] spp_pcap: refactor comments of spp_pcap ogawa.yasufumi
2019-05-31 8:52 ` [spp] [PATCH 09/10] spp_pcap: rename spp_get_core_status ogawa.yasufumi
2019-05-31 8:52 ` [spp] [PATCH 10/10] spp_pcap: revise name of vars for parser error 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=1559292762-27042-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).