From: yasufum.o@gmail.com
To: spp@dpdk.org, ferruh.yigit@intel.com, yasufum.o@gmail.com
Subject: [spp] [PATCH 0/5] Revising logs and comments in shared
Date: Mon, 24 Jun 2019 11:23:20 +0900 [thread overview]
Message-ID: <20190624022325.18695-1-yasufum.o@gmail.com> (raw)
From: Yasufumi Ogawa <yasufum.o@gmail.com>
This series of patches is to refactor log messages and comments for
code maintenance.
* Rename functions start with `dump_` used for not dumping messages but
logging.
* Revise ambiguous variables start with `num_` used for "Number of" or
exact number. Former one is renamed as starts with `nof_`.
* Revise terms of funcs and vars which are not correct meaning for
usages.
Yasufumi Ogawa (5):
shared/sec: revise comments in cmd_utils.h
shared/sec: rename funcs start with dump
shared/sec: revise member of struct for interface
shared/sec: rename defines for length of str
shared/sec: add prefix to defines of worker types
src/mirror/spp_mirror.c | 6 +-
.../secondary/spp_worker_th/cmd_parser.c | 4 +-
.../secondary/spp_worker_th/cmd_runner.c | 11 +-
.../secondary/spp_worker_th/cmd_utils.c | 88 ++---
.../secondary/spp_worker_th/cmd_utils.h | 352 +++++++-----------
src/shared/secondary/spp_worker_th/vf_deps.h | 15 +-
src/vf/classifier_mac.c | 18 +-
src/vf/spp_forward.c | 8 +-
8 files changed, 196 insertions(+), 306 deletions(-)
--
2.17.1
next reply other threads:[~2019-06-24 2:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 2:23 yasufum.o [this message]
2019-06-24 2:23 ` [spp] [PATCH 1/5] shared/sec: revise comments in cmd_utils.h yasufum.o
2019-06-24 2:23 ` [spp] [PATCH 2/5] shared/sec: rename funcs start with dump yasufum.o
2019-06-24 2:23 ` [spp] [PATCH 3/5] shared/sec: revise member of struct for interface yasufum.o
2019-06-24 2:23 ` [spp] [PATCH 4/5] shared/sec: rename defines for length of str yasufum.o
2019-06-24 2:23 ` [spp] [PATCH 5/5] shared/sec: add prefix to defines of worker types yasufum.o
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=20190624022325.18695-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).