Soft Patch Panel
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: x-fn-spp@sl.ntt-tx.co.jp, spp@dpdk.org
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: Re: [spp] [PATCH 4/9] spp_vf: add BSD license
Date: Thu, 8 Feb 2018 15:14:58 +0000	[thread overview]
Message-ID: <62f1b786-d541-bd82-4618-4e192f088ddc@intel.com> (raw)
In-Reply-To: <201802080556.w185uBLt011286@imss03.silk.ntt-tx.co.jp>

On 2/8/2018 5:56 AM, x-fn-spp@sl.ntt-tx.co.jp wrote:
> From: Kentaro Watanabe <watanabe.kentaro.z01@as.ntt-tx.co.jp>
> 
> Signed-off-by: Kentaro Watanabe <watanabe.kentaro.z01@as.ntt-tx.co.jp>
> Signed-off-by: Naoki Takada <takada.naoki@lab.ntt.co.jp>
> ---
>  src/vf/classifier_mac.c   | 33 +++++++++++++++++++++++++++++++++
>  src/vf/classifier_mac.h   | 33 +++++++++++++++++++++++++++++++++
>  src/vf/command_conn.c     | 33 +++++++++++++++++++++++++++++++++
>  src/vf/command_conn.h     | 33 +++++++++++++++++++++++++++++++++
>  src/vf/command_dec.c      | 33 +++++++++++++++++++++++++++++++++
>  src/vf/command_dec.h      | 33 +++++++++++++++++++++++++++++++++
>  src/vf/command_proc.c     | 33 +++++++++++++++++++++++++++++++++
>  src/vf/command_proc.h     | 33 +++++++++++++++++++++++++++++++++
>  src/vf/ringlatencystats.c | 33 +++++++++++++++++++++++++++++++++
>  src/vf/ringlatencystats.h | 33 +++++++++++++++++++++++++++++++++
>  src/vf/spp_forward.c      | 33 +++++++++++++++++++++++++++++++++
>  src/vf/spp_forward.h      | 33 +++++++++++++++++++++++++++++++++
>  src/vf/spp_vf.c           | 33 +++++++++++++++++++++++++++++++++
>  src/vf/spp_vf.h           | 33 +++++++++++++++++++++++++++++++++
>  src/vf/string_buffer.c    | 33 +++++++++++++++++++++++++++++++++
>  src/vf/string_buffer.h    | 33 +++++++++++++++++++++++++++++++++

This patch adds a fixed license header which has Intel as copyright owner. But
there are some file added by ntt, like spp_vf, you may want to keep your
copyright for those files.

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.

<...>

  reply	other threads:[~2018-02-08 15:15 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 [this message]
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
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=62f1b786-d541-bd82-4618-4e192f088ddc@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=spp@dpdk.org \
    --cc=x-fn-spp@sl.ntt-tx.co.jp \
    /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).