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/6] Revise name of funcs for parsing actions
Date: Tue, 21 May 2019 11:31:58 +0900 [thread overview]
Message-ID: <1558405924-8303-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
SPP worker processes defines a series of actions for given resources,
but the name of functions for parsing the actinos are not incorrect or
ambiguous in meaning. This series of update is to revise them.
Yasufumi Ogawa (6):
shared/sec: rename parse comp action val
shared/sec: rename func for parsing comp name
shared/sec: refacotr comments for parse comp name
shared/sec: rename func for parsing lcore ID
shared/sec: rename func of parsing comp type
shared/sec: rename parsing comp action
.../secondary/spp_worker_th/cmd_parser.c | 63 ++++++++++---------
src/shared/secondary/spp_worker_th/spp_proc.c | 2 +-
2 files changed, 36 insertions(+), 29 deletions(-)
--
2.17.1
next 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 ogawa.yasufumi [this message]
2019-05-21 2:31 ` [spp] [PATCH 1/6] shared/sec: rename parse comp action val ogawa.yasufumi
2019-05-21 2:32 ` [spp] [PATCH 2/6] shared/sec: rename func for parsing comp name ogawa.yasufumi
2019-05-21 2:32 ` [spp] [PATCH 3/6] shared/sec: refacotr comments for parse " 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-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).