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/5] Fix bugs of SPP CLI
Date: Mon, 4 Feb 2019 12:11:14 +0900 [thread overview]
Message-ID: <1549249879-31580-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
* Add checking for `vf` command to avoid errors of invalid resource
configuration and invlalid command syntax.
* Correct logging history.
* Correct parsing command line of `pri` for completion.
Yasufumi Ogawa (5):
controller: fix bug to add vf comps on same core
controller: add checking syntax for vf port cmd
controller: fix bug of history command
controller: fix bug of completion of pri
controller: refactor configuration of logfile
src/controller/commands/pri.py | 90 ++++++++++++++++++++++--------------------
src/controller/commands/vf.py | 29 ++++++++------
src/controller/shell.py | 40 +++++++------------
src/controller/spp_common.py | 4 +-
4 files changed, 82 insertions(+), 81 deletions(-)
--
2.7.4
next reply other threads:[~2019-02-04 3:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 3:11 ogawa.yasufumi [this message]
2019-02-04 3:11 ` [spp] [PATCH 1/5] controller: fix bug to add vf comps on same core ogawa.yasufumi
2019-02-04 3:11 ` [spp] [PATCH 2/5] controller: add checking syntax for vf port cmd ogawa.yasufumi
2019-02-04 3:11 ` [spp] [PATCH 3/5] controller: fix bug of history command ogawa.yasufumi
2019-02-04 3:11 ` [spp] [PATCH 4/5] controller: fix bug of completion of pri ogawa.yasufumi
2019-02-04 3:11 ` [spp] [PATCH 5/5] controller: refactor configuration of logfile 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=1549249879-31580-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).