Soft Patch Panel
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: spp@dpdk.org
Subject: Re: [spp] [PATCH v2 0/9] Update for spp_vf
Date: Fri, 2 Mar 2018 17:20:14 +0000	[thread overview]
Message-ID: <34175f51-469e-229a-7eba-73da60b89069@intel.com> (raw)
In-Reply-To: <1519734869-21582-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp>

On 2/27/2018 12:34 PM, ogawa.yasufumi@lab.ntt.co.jp wrote:
> From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
> 
> Hi,
> 
> It is 2nd version for updating spp_vf.
> 
> This update includes vlan support as a new feature, bug fix
> and refactoring remained as TODO.
> 
> Hiroyuki Nakamura (3):
>   spp_vf: add VLAN tag operate function to port
>   spp_vf: refactor struct and variable names
>   spp_vf: add VID classification to the classifier
> 
> Kentaro Watanabe (5):
>   spp_vf: add vlan feature
>   spp_vf: refactor comments and variable names
>   spp_vf: change header file to doxygen format
>   spp_vf: add BSD license
>   spp_vf: change log level setting
> 
> Yasufumi Ogawa (1):
>   spp_vf: refactor to comply with coding style

Series applied to dpdk-next-net/master, thanks.

Only updated sub-system prefix from "spp_vf:" to "vf:". To prevent confusion
between spp_vf.py which also uses same "spp_vf:" prefix.

And spp is not adding much context here indeed, I think after this we can
continue without "spp_" part, like "vf: ", "vm: ", "nfv: " ...

Thanks,
ferruh

  parent reply	other threads:[~2018-03-02 17:20 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
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   ` Ferruh Yigit [this message]
2018-03-03 13:39     ` [spp] [PATCH v2 0/9] Update for spp_vf 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=34175f51-469e-229a-7eba-73da60b89069@intel.com \
    --to=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).