From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Nakamura Hioryuki <nakamura.hiroyuki@po.ntt-tx.co.jp>, spp@dpdk.org
Subject: Re: [spp] [spp 02181] Re: [PATCH 4/9] spp_vf: add BSD license
Date: Fri, 16 Feb 2018 18:01:21 +0900 [thread overview]
Message-ID: <4b69b78a-832a-35a0-b82e-932ec49e5629@lab.ntt.co.jp> (raw)
In-Reply-To: <a4d5c05d-5f6c-fe48-48e2-14e737beaa50@intel.com>
On 2018/02/15 19:22, Ferruh Yigit wrote:
> On 2/9/2018 7:16 AM, Yasufumi Ogawa wrote:
>> On 2018/02/09 12:03, Nakamura Hioryuki wrote:
>>> Thank you for reviewing and pointing out.
>>>
>>> Revised patches are posted in the following emails.
>>>
>>>> Also DPDK is switching to SPDX tags, that makes license headers easy, we can
>>>> think about same thing for spp. Not for this patchset, but for future.
>>>
>>> Ok, Thank you for information.
>>> "spp_vf: add BSD license" is deleted from revised patchset, we will make
>>> change license header for future.
>>>
>>> Also, "[PATCH 8/9] spp_vf: refactor to comply with coding style" is
>>> deleted, because this will conflict with Yasufumi’s patch
>>> "[PATCH 2/2] spp_vf: update to improve usability"
>>>
>>
>> Hi Hiroyuki, Ferruh
>>
>> Thank you for comments for licensing. I did not be aware switching SPDX.
>> I think we should add this topic in next TODOs.
>>
>> Hiroyuki, thanks for contribution. However, I think it is not needed to
>> revise license only for spp_vf at this time. We should revise all of spp.
>>
>> Ferruh, If you find Hiroyuki's reply after merged previous patches,
>> could you do not re-merge revised patches to avoid to waste your time? I
>> would like to update all of files and send another patches later.
>
> Hi Yasufumi,
>
> Sure, I will wait for your patchset.
>
> btw, DPDK v18.02 is out now and available for testing with spp.
>
> Thanks,
> ferruh
Thanks Ferruh! I will try SPP with latest DPDK v18.02!
Before update the version of SPP, I would like to merge patches from
Kentaro and me. Could you check and merge it ?
Kentaro sent 9 patches
[spp] [PATCH 1/9] spp_vf: refactor to comply with coding rule
...
[spp] [PATCH 9/9] spp_vf: change log level setting
and I sent 5 patches.
[spp] [PATCH 1/3] spp_nfv: enable to patch ports with resource ID
[spp] [PATCH 2/3] spp: add validation for patch command
[spp] [PATCH 3/3] spp_vm: enable to patch ports with resource ID
[spp] [PATCH 1/2] spp: update to improve usability
[spp] [PATCH 2/2] spp_vf: update to improve usability
Thanks,
Yasufumi
>
>
>>
>> Thanks,
>> Yasufumi
>>
>
>
>
--
Yasufumi Ogawa
NTT Network Service Systems Labs
next prev parent reply other threads:[~2018-02-16 9:02 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 5:51 [spp] [PATCH 1/9] spp_vf: refactor to comply with coding rule x-fn-spp
2018-02-08 5:55 ` [spp] [PATCH 2/9] spp_vf: refactor comments and variable names x-fn-spp
2018-02-08 5:56 ` [spp] [PATCH 3/9] spp_vf: change header file to doxygen format x-fn-spp
2018-02-08 5:56 ` [spp] [PATCH 4/9] spp_vf: add BSD license x-fn-spp
2018-02-08 15:14 ` Ferruh Yigit
2018-02-09 3:03 ` [spp] [spp 02181] " Nakamura Hioryuki
2018-02-09 3:39 ` [spp] [PATCH 1/7] spp_vf: refactor to comply with coding rule x-fn-spp
2018-02-09 3:39 ` [spp] [PATCH 2/7] spp_vf: refactor comments and variable names x-fn-spp
2018-02-09 3:39 ` [spp] [PATCH 3/7] spp_vf: change header file to doxygen format x-fn-spp
2018-02-09 3:40 ` [spp] [PATCH 4/7] spp_vf: add VLAN tag operate function to port x-fn-spp
2018-02-09 3:40 ` [spp] [PATCH 5/7] spp_vf: refactor struct and variable names x-fn-spp
2018-02-09 3:40 ` [spp] [PATCH 6/7] spp_vf: add VID classification to the classifier x-fn-spp
2018-02-09 3:40 ` [spp] [PATCH 7/7] spp_vf: change log level setting x-fn-spp
2018-02-09 7:16 ` [spp] [spp 02181] Re: [PATCH 4/9] spp_vf: add BSD license Yasufumi Ogawa
2018-02-15 10:22 ` Ferruh Yigit
2018-02-16 9:01 ` Yasufumi Ogawa [this message]
2018-02-16 14:40 ` Ferruh Yigit
2018-02-19 1:59 ` Yasufumi Ogawa
2018-02-22 8:10 ` Yasufumi Ogawa
2018-02-22 10:13 ` Ferruh Yigit
2018-02-22 10:19 ` Thomas Monjalon
2018-02-22 10:26 ` Ferruh Yigit
2018-02-22 11:02 ` Yasufumi Ogawa
2018-02-08 5:56 ` [spp] [PATCH 5/9] spp_vf: add VLAN tag operate function to port x-fn-spp
2018-02-08 5:56 ` [spp] [PATCH 6/9] spp_vf: refactor struct and variable names x-fn-spp
2018-02-08 5:56 ` [spp] [PATCH 7/9] spp_vf: add VID classification to the classifier x-fn-spp
2018-02-08 5:56 ` [spp] [PATCH 8/9] spp_vf: refactor to comply with coding style x-fn-spp
2018-02-08 5:56 ` [spp] [PATCH 9/9] spp_vf: change log level setting x-fn-spp
2018-02-08 7:45 ` [spp] [PATCH 1/9] spp_vf: refactor to comply with coding rule Yasufumi Ogawa
2018-02-27 12:34 ` [spp] [PATCH v2 0/9] Update for spp_vf ogawa.yasufumi
2018-02-27 12:34 ` [spp] [PATCH v2 1/9] spp_vf: add vlan feature ogawa.yasufumi
2018-02-27 12:34 ` [spp] [PATCH v2 3/9] spp_vf: change header file to doxygen format ogawa.yasufumi
2018-02-27 12:34 ` [spp] [PATCH v2 4/9] spp_vf: add BSD license ogawa.yasufumi
2018-02-27 12:34 ` [spp] [PATCH v2 5/9] spp_vf: add VLAN tag operate function to port ogawa.yasufumi
2018-02-27 12:34 ` [spp] [PATCH v2 6/9] spp_vf: refactor struct and variable names ogawa.yasufumi
2018-02-27 12:34 ` [spp] [PATCH v2 7/9] spp_vf: add VID classification to the classifier ogawa.yasufumi
2018-02-27 12:34 ` [spp] [PATCH v2 8/9] spp_vf: refactor to comply with coding style ogawa.yasufumi
2018-02-27 12:34 ` [spp] [PATCH v2 9/9] spp_vf: change log level setting ogawa.yasufumi
2018-03-02 17:20 ` [spp] [PATCH v2 0/9] Update for spp_vf Ferruh Yigit
2018-03-03 13:39 ` Yasufumi Ogawa
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=4b69b78a-832a-35a0-b82e-932ec49e5629@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=nakamura.hiroyuki@po.ntt-tx.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).