From: yasufum.o@gmail.com
To: spp@dpdk.org, ferruh.yigit@intel.com, yasufum.o@gmail.com
Subject: [spp] [PATCH 0/2] Update recipe scripts
Date: Mon, 1 Jul 2019 13:12:42 +0900 [thread overview]
Message-ID: <20190701041244.34176-1-yasufum.o@gmail.com> (raw)
From: Yasufumi Ogawa <yasufum.o@gmail.com>
Recipe scripts for spp_nfv and spp_vf are not maintained and failed to
run because command syntax is too old. This series of patches is to
update them to the latest syntax as described in documents.
Yasufumi Ogawa (2):
recipes: update old rcps for spp_nfv
recipes: update old rcps for spp_vf
recipes/usecases/spp_nfv/dual_bidir.rcps | 10 ++++-----
recipes/usecases/spp_nfv/dual_loopback.rcps | 9 ++++----
recipes/usecases/spp_nfv/ring_dual_bidir.rcps | 22 +++++++++----------
.../usecases/spp_nfv/ring_dual_unidir.rcps | 16 ++++++--------
recipes/usecases/spp_nfv/single_bidir.rcps | 8 +++----
recipes/usecases/spp_nfv/single_loopback.rcps | 4 ++++
recipes/usecases/spp_nfv/vhost_unidir.rcps | 11 +++++-----
.../ssh_login/setup/1-start_components.rcps | 7 ------
.../ssh_login/setup/1_start_components.rcps | 7 ++++++
.../ssh_login/setup/2-add_ports_path1.rcps | 20 -----------------
.../ssh_login/setup/2_add_ports_path1.rcps | 18 +++++++++++++++
.../ssh_login/setup/3-reg_mac_path1.rcps | 3 ---
.../ssh_login/setup/3_reg_mac_path1.rcps | 3 +++
.../ssh_login/setup/4-start_components.rcps | 7 ------
.../ssh_login/setup/4_start_components.rcps | 7 ++++++
.../ssh_login/setup/5-add_ports_path2.rcps | 20 -----------------
.../ssh_login/setup/5_add_ports_path2.rcps | 19 ++++++++++++++++
.../ssh_login/setup/6-reg_mac_path2.rcps | 3 ---
.../ssh_login/setup/6_reg_mac_path2.rcps | 3 +++
.../spp_vf/ssh_login/setup/7-flush.rcps | 1 -
20 files changed, 97 insertions(+), 101 deletions(-)
create mode 100644 recipes/usecases/spp_nfv/single_loopback.rcps
delete mode 100644 recipes/usecases/spp_vf/ssh_login/setup/1-start_components.rcps
create mode 100644 recipes/usecases/spp_vf/ssh_login/setup/1_start_components.rcps
delete mode 100644 recipes/usecases/spp_vf/ssh_login/setup/2-add_ports_path1.rcps
create mode 100644 recipes/usecases/spp_vf/ssh_login/setup/2_add_ports_path1.rcps
delete mode 100644 recipes/usecases/spp_vf/ssh_login/setup/3-reg_mac_path1.rcps
create mode 100644 recipes/usecases/spp_vf/ssh_login/setup/3_reg_mac_path1.rcps
delete mode 100644 recipes/usecases/spp_vf/ssh_login/setup/4-start_components.rcps
create mode 100644 recipes/usecases/spp_vf/ssh_login/setup/4_start_components.rcps
delete mode 100644 recipes/usecases/spp_vf/ssh_login/setup/5-add_ports_path2.rcps
create mode 100644 recipes/usecases/spp_vf/ssh_login/setup/5_add_ports_path2.rcps
delete mode 100644 recipes/usecases/spp_vf/ssh_login/setup/6-reg_mac_path2.rcps
create mode 100644 recipes/usecases/spp_vf/ssh_login/setup/6_reg_mac_path2.rcps
delete mode 100644 recipes/usecases/spp_vf/ssh_login/setup/7-flush.rcps
--
2.17.1
next reply other threads:[~2019-07-01 4:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 4:12 yasufum.o [this message]
2019-07-01 4:12 ` [spp] [PATCH 1/2] recipes: update old rcps for spp_nfv yasufum.o
2019-07-01 4:12 ` [spp] [PATCH 2/2] recipes: update old rcps for spp_vf 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=20190701041244.34176-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).