From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
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: Thu, 22 Feb 2018 10:26:55 +0000 [thread overview]
Message-ID: <d6ae82c7-a03a-bca3-8ac2-b95b9fd43e8c@intel.com> (raw)
In-Reply-To: <1545048.PFpTTTFbJg@xps>
On 2/22/2018 10:19 AM, Thomas Monjalon wrote:
> 22/02/2018 11:13, Ferruh Yigit:
>> On 2/22/2018 8:10 AM, Yasufumi Ogawa wrote:
>>> I did not think of patchwork. I think it is good idea if SPP can use
>>> patchwork for patch management.
>>>
>>> Although I am not sure if it is possible to use patchwork on dpdk.org,
>>> do you have any idea for using it for SPP, or allowed only for 'dev'?
>>
>> I know from other projects, it is technically possible to share single patchwork
>> for multiple mail list. But not sure how difficult to setup or maintain that model.
>>
>> cc'ed Thomas for comment.
>
> Yes we could do it.
> But honestly, it is not the right timing.
> We should migrate to a new server with a new patchwork version first.
> I can add this requirement in the migration task.
> It may take few months before it is done. Is it OK?
I believe it is not urgent, doing this while migrating to new server makes sense
to me.
next prev parent reply other threads:[~2018-02-22 10:26 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
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 [this message]
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=d6ae82c7-a03a-bca3-8ac2-b95b9fd43e8c@intel.com \
--to=ferruh.yigit@intel.com \
--cc=nakamura.hiroyuki@po.ntt-tx.co.jp \
--cc=ogawa.yasufumi@lab.ntt.co.jp \
--cc=spp@dpdk.org \
--cc=thomas@monjalon.net \
/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).