From: ogawa.yasufumi@lab.ntt.co.jp
To: ferruh.yigit@intel.com
Cc: spp@dpdk.org, Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Subject: [spp] [PATCH v2 0/3] Update for Python 3 support
Date: Thu, 24 May 2018 05:11:47 +0900 [thread overview]
Message-ID: <20180523201150.23042-1-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <20180515012004.8726-1-ogawa.yasufumi@lab.ntt.co.jp>
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Hi,
This patch set is for adding Python 3 support. This update is needed
to follow the previous patches of license update bacause it changes the
top of files and it affects codes importing modules. The difference
from v1 is only the number of line for the importing.
Thanks,
Yasufumi
Yasufumi Ogawa (3):
controller: change importing for python3
controller: fix encoding for socket
docs: add description for python 3 support
docs/guides/setup/getting_started.rst | 17 ++++++++++++--
src/controller/conn_thread.py | 19 ++++++++-------
src/controller/shell.py | 34 ++++++++++++++-------------
src/controller/spp.py | 21 +++++++++--------
src/controller/spp_common.py | 2 +-
src/controller/topo.py | 4 ++--
src/spp.py | 1 +
7 files changed, 59 insertions(+), 39 deletions(-)
--
2.17.0
next prev parent reply other threads:[~2018-05-23 20:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 1:20 [spp] [PATCH " ogawa.yasufumi
2018-05-15 1:20 ` [spp] [PATCH 1/3] controller: change importing for python3 ogawa.yasufumi
2018-05-15 1:20 ` [spp] [PATCH 2/3] controller: fix encoding for socket ogawa.yasufumi
2018-05-15 1:20 ` [spp] [PATCH 3/3] docs: add description for python 3 support ogawa.yasufumi
2018-05-23 20:11 ` ogawa.yasufumi [this message]
2018-05-23 20:11 ` [spp] [PATCH v2 1/3] controller: change importing for python3 ogawa.yasufumi
2018-05-23 20:11 ` [spp] [PATCH v2 2/3] controller: fix encoding for socket ogawa.yasufumi
2018-05-23 20:11 ` [spp] [PATCH v2 3/3] docs: add description for python 3 support ogawa.yasufumi
2018-05-24 13:18 ` [spp] [PATCH v2 0/3] Update for Python " Ferruh Yigit
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=20180523201150.23042-1-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).