From: ogawa.yasufumi@lab.ntt.co.jp
To: ferruh.yigit@intel.com, spp@dpdk.org, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 0/2] Change response of _get_client_id in spp_nfv
Date: Tue, 15 Jan 2019 21:27:58 +0900 [thread overview]
Message-ID: <1547555280-11736-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Spp_nfv returns its client ID as plain text. However, it should be
JSON as same as other secondary processes. This series of update is
to change the format in both of sender of spp_nfv and receiver of
spp-ctl.
Yasufumi Ogawa (2):
spp_nfv: change _get_client_id to return JSON msg
spp-ctl: change NfvProc to parse JSON msg
src/nfv/commands.h | 6 +++++-
src/spp-ctl/spp_proc.py | 16 ++++++----------
2 files changed, 11 insertions(+), 11 deletions(-)
--
2.17.1
next reply other threads:[~2019-01-15 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 12:27 ogawa.yasufumi [this message]
2019-01-15 12:27 ` [spp] [PATCH 1/2] spp_nfv: change _get_client_id to return JSON msg ogawa.yasufumi
2019-01-15 12:28 ` [spp] [PATCH 2/2] spp-ctl: change NfvProc to parse " 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=1547555280-11736-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).