From: yasufum.o@gmail.com
To: spp@dpdk.org, ferruh.yigit@intel.com, yasufum.o@gmail.com
Subject: [spp] [PATCH 0/2] Rename struct cmd_response
Date: Mon, 24 Jun 2019 16:10:49 +0900 [thread overview]
Message-ID: <20190624071051.23342-1-yasufum.o@gmail.com> (raw)
From: Yasufumi Ogawa <yasufum.o@gmail.com>
Struct cmd_response is to define a set of combinations of tag and ope
function, so the name is not appropriate considering this feature.
This update is to rename it to `cmd_res_formatter_ops` for spp_vf,
spp_mirror and spp_pcap.
Yasufumi Ogawa (2):
shared/sec: change name of struct cmd_response
spp_pcap: change name of struct cmd_response
src/pcap/cmd_runner.c | 8 ++++----
.../secondary/spp_worker_th/cmd_res_formatter.c | 13 ++++++-------
.../secondary/spp_worker_th/cmd_res_formatter.h | 11 +++++------
3 files changed, 15 insertions(+), 17 deletions(-)
--
2.17.1
next reply other threads:[~2019-06-24 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 7:10 yasufum.o [this message]
2019-06-24 7:10 ` [spp] [PATCH 1/2] shared/sec: change name of " yasufum.o
2019-06-24 7:10 ` [spp] [PATCH 2/2] spp_pcap: " 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=20190624071051.23342-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).