From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
x-fn-spp@sl.ntt-tx.co.jp, spp@dpdk.org
Subject: Re: [spp] Patches for spp_vf on DPDK17.11
Date: Mon, 15 Jan 2018 11:08:22 +0900 [thread overview]
Message-ID: <042a7784-c4e2-4657-7e40-663adede6322@lab.ntt.co.jp> (raw)
In-Reply-To: <7de5cc0e-2bb9-2e66-6c5c-2d690f15f2ab@intel.com>
Hi Ferruh,
Sorry for ambiguously for my reply. I would like to merge both of series
including later 4 patches. I will send acked-by for future patches.
> And another question is current head in spp tested on v17.11? Is it
safe to tag
> it as v17.11?
Thank you for your suggestion. I have tested with DPDK 17.11 and we
should to do tagging. Considering that Hiroyuki is going to send another
patches for documentation, I would like to send a patch for updating
Makefile to tag 17.11 soon after him.
Thanks,
Yasufumi
On 2018/01/13 22:38, Ferruh Yigit wrote:
> On 1/10/2018 7:53 AM, Yasufumi Ogawa wrote:
>> Hi Hiroyuki, Ferruh,
>>
>> Thanks Hiroyuki for considering to update. I tried to compile and run it
>> without errors or warnings for DPDK 17.11. It seems to work fine.
>>
>> As Hiroyuki mentioned in previously, there are still remained warnings
>> for coding style from checkpatch and we need to fix them as the next
>> task. Thank you for your contributions!
>>
>> Ferruh, could you merge patches from Hiroyuki?
>
> Hiroyuki thanks for the patches, and Yasufumi thank you for the review and testing.
>
> Yasufumi,
>
> There are two patchsets, one is this one with 4 patches and other is with 57
> patches. And as far as I can this one depends the other one.
>
> Are you OK to getting both of the patchsets?
> btw, I will add your ack explicitly to all.
>
> And another question is current head in spp tested on v17.11? Is it safe to tag
> it as v17.11?
>
> Thanks,
> ferruh
>
>>
>> Thanks,
>> Yasufumi
>>
>> On 2018/01/10 11:46, x-fn-spp@sl.ntt-tx.co.jp wrote:
>>> Hi everyone,
>>>
>>> Last year, we've sent some patches for spp_vf on DPDK17.08.
>>> In addition to these patches, we are now ready to contribute
>>> the patches for spp_vf on DPDK17.11.
>>>
>>> Code changes will be posted in the following emails.
>>>
>>>
>>
>>
>
>
>
--
Yasufumi Ogawa
NTT Network Service Systems Labs
next prev parent reply other threads:[~2018-01-15 2:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 2:46 x-fn-spp
2018-01-10 2:47 ` [spp] [PATCH 1/4] spp_vf: fix to eliminate jansson package x-fn-spp
2018-01-19 0:37 ` Yasufumi Ogawa
2018-01-10 2:47 ` [spp] [PATCH 2/4] spp_vf: support cancel command x-fn-spp
2018-01-10 2:48 ` [spp] [PATCH 3/4] spp_vf: change type of port_id to uint16_t x-fn-spp
2018-01-10 2:48 ` [spp] [PATCH 4/4] spp_vf: fix bug of status command x-fn-spp
2018-01-10 7:53 ` [spp] Patches for spp_vf on DPDK17.11 Yasufumi Ogawa
2018-01-13 13:38 ` Ferruh Yigit
2018-01-15 2:08 ` Yasufumi Ogawa [this message]
2018-01-19 0:30 ` Yasufumi Ogawa
2018-01-22 14:04 ` Ferruh Yigit
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=042a7784-c4e2-4657-7e40-663adede6322@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=ferruh.yigit@intel.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).