Soft Patch Panel
 help / color / mirror / Atom feed
From: yasufum.o@gmail.com
To: spp@dpdk.org, ferruh.yigit@intel.com, yasufum.o@gmail.com
Subject: [spp] [PATCH 0/3] Rename spp_port_rxtx
Date: Mon, 24 Jun 2019 17:40:40 +0900	[thread overview]
Message-ID: <20190624084043.23718-1-yasufum.o@gmail.com> (raw)

From: Yasufumi Ogawa <yasufum.o@gmail.com>

Enum `spp_port_rxtx` is used as a port attribute to have a direction,
RX or TX. It is not used to have a set of RX and TX, but defines the
direction. So, It is better to be named as `port_dir` or so. This series
of patches is to rename this enum for spp_vf, spp_mirror and spp_pcap.

Yasufumi Ogawa (3):
  shared/sec: revise enum spp_port_rxtx
  shared/sec: rename members of enum sppwk_port_dir
  spp_pcap: revise enum spp_port_rxtx

 src/mirror/mir_cmd_runner.c                   | 24 +++++------
 src/pcap/cmd_runner.c                         |  8 ++--
 src/pcap/cmd_utils.h                          | 17 ++++----
 .../secondary/spp_worker_th/cmd_parser.c      | 18 ++++-----
 .../secondary/spp_worker_th/cmd_parser.h      |  4 +-
 .../spp_worker_th/cmd_res_formatter.c         | 16 ++++----
 .../spp_worker_th/cmd_res_formatter.h         |  6 +--
 .../secondary/spp_worker_th/cmd_utils.c       | 17 ++++----
 .../secondary/spp_worker_th/cmd_utils.h       | 27 ++++++-------
 src/shared/secondary/spp_worker_th/spp_port.c | 40 +++++++++----------
 src/shared/secondary/spp_worker_th/spp_port.h |  4 +-
 src/vf/vf_cmd_runner.c                        | 32 +++++++--------
 12 files changed, 104 insertions(+), 109 deletions(-)

-- 
2.17.1


             reply	other threads:[~2019-06-24  8:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-24  8:40 yasufum.o [this message]
2019-06-24  8:40 ` [spp] [PATCH 1/3] shared/sec: revise enum spp_port_rxtx yasufum.o
2019-06-24  8:40 ` [spp] [PATCH 2/3] shared/sec: rename members of enum sppwk_port_dir yasufum.o
2019-06-24  8:40 ` [spp] [PATCH 3/3] spp_pcap: revise enum spp_port_rxtx 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=20190624084043.23718-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).