From: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: spp@dpdk.org, Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Subject: Re: [spp] [spp 02934] Re: [PATCH] docs: fix typos of command example
Date: Mon, 09 Jul 2018 11:18:36 +0900 [thread overview]
Message-ID: <201807090219.w692JHGH032279@ccmail04.silk.ntt-tx.co.jp> (raw)
In-Reply-To: <cb06f778-f458-f269-f2d7-8940542cccd8@lab.ntt.co.jp>
Hello Ferruh-san,
I am planning to contribute on SPP.
I think it is better that the base line source code be 18.05.
Though I think you might be super busy,
I am waiting remained patches merged into master branch ASAP.
Thanks in advance.
BR,
Hideyuki Yamashita
> Hi Ferruh,
>
> Many thnaks for your reviewing and maintaining for SPP. I am appreciate your cooperation because SPP has grown up and the number of contributors is increased gradually.
>
> By the way, could you check remained patches for merging? If there are OK, I would like to fix to update for SPP 18.05. Here is a list of patches.
>
> Thanks,
> Yasufumi
>
> - [PATCH v3 0/3] docs:improvement of document under VF directory
> docs: add how to install qemu 2.7
> docs: correct incorrect SPP git URL
> docs: delete unsupported SPP VF Secondary Command
>
> - [PATCH 0/3] Introduce recipes as config
> recipes: add recipes directory
> recipes: update SPP usecases
> recipes: update SPP_VF usecases
>
> - [PATCH 0/2] Update doc for inappropriate link
> docs: add label to index of command reference
> docs: update link of command reference
>
> - [PATCH v2 00/15] Fix mistakes of SPP container documentation
> docs: add index of SPP container tool
> docs: add overview of SPP container
> docs: add overview image of SPP container
> docs: add getting started guide of SPP container
> docs: add image of example for gsg
> docs: add install guide for SPP container
> docs: add build image guide for SPP container
> docs: add manual for app container launchers
> docs: add use cases of SPP container
> docs: add usecase image of testing vhost
> docs: add usecase image of testing ring
> docs: add usecase image of pktgen and l2fwd
> docs: add usecase image of using less lcores
> docs: add usecase image of load balancer
> docs: add how to develop guide for SPP container
>
> - [PATCH 00/15] Add SPP container tools
> tools/sppc: add SPP container build tool
> tools/sppc: add dockerfiles for DPDK
> tools/sppc: add dockerfiles for pktgen
> tools/sppc: add dockerfiles for SPP
> tools/sppc: add spp-primary app continer
> tools/sppc: add spp-nfv app continer
> tools/sppc: add spp-vm app continer
> tools/sppc: add l2fwd app continer
> tools/sppc: add testpmd app continer
> tools/sppc: add l3fwd app continer
> tools/sppc: add pktgen app continer
> tools/sppc: add load-balancer app continer
> tools/sppc: add helloworld app continer
> tools/sppc: add helper script for build
> tools/sppc: add spp launcher script
>
> - [PATCH 0/7] patches for DPDK v18.05
> spp_nfv: fix deprecated use of rte_eth_dev_count
> spp_primary: fix deprecated use of rte_eth_dev_count
> spp_vm: fix deprecated use of rte_eth_dev_count
> spp_vf: fix deprecated use of rte_eth_dev_count
> spp_vm: fix changing spec of rte_mem_config
> shared: fix for updating API of DPDK v18.05
> spp_vm: add DALLOW_EXPERIMENTAL_API on CFLA
>
> On 2018/06/27 20:00, Ferruh Yigit wrote:
> > On 6/12/2018 12:16 PM, ogawa.yasufumi@lab.ntt.co.jp wrote:
> >> From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
> >>
> >> Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
> >
> > Applied, thanks.
> >
> >
>
> -- Yasufumi Ogawa
> NTT Network Service Systems Labs
>
next prev parent reply other threads:[~2018-07-09 2:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 11:16 [spp] " ogawa.yasufumi
2018-06-27 11:00 ` Ferruh Yigit
2018-07-03 7:23 ` Yasufumi Ogawa
2018-07-09 2:18 ` Hideyuki Yamashita [this message]
2018-08-15 15:48 ` [spp] [spp 02934] " Ferruh Yigit
2018-08-16 8:01 ` Thomas Monjalon
2018-08-20 3:08 ` Yasufumi Ogawa
2018-08-22 8:54 ` 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=201807090219.w692JHGH032279@ccmail04.silk.ntt-tx.co.jp \
--to=yamashita.hideyuki@po.ntt-tx.co.jp \
--cc=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).