From: Ferruh Yigit <ferruh.yigit@intel.com>
To: ogawa.yasufumi@lab.ntt.co.jp
Cc: spp@dpdk.org
Subject: Re: [spp] [PATCH v2 0/3] Update for Python 3 support
Date: Thu, 24 May 2018 14:18:40 +0100 [thread overview]
Message-ID: <4b02b401-dbe3-cb10-e363-37d02b9f5f82@intel.com> (raw)
In-Reply-To: <20180523201150.23042-1-ogawa.yasufumi@lab.ntt.co.jp>
On 5/23/2018 9:11 PM, ogawa.yasufumi@lab.ntt.co.jp wrote:
> 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
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-05-24 13:18 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 ` [spp] [PATCH v2 0/3] Update for Python " ogawa.yasufumi
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 ` Ferruh Yigit [this message]
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=4b02b401-dbe3-cb10-e363-37d02b9f5f82@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ogawa.yasufumi@lab.ntt.co.jp \
--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).