From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
To: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
Cc: spp@dpdk.org, ferruh.yigit@intel.com
Subject: Re: [spp] [spp 03234] [PATCH 0/2] Fix compile error with DPDK v18.08
Date: Wed, 7 Nov 2018 12:03:17 +0900 [thread overview]
Message-ID: <b7586534-1679-9642-f367-61d3e9f184ea@lab.ntt.co.jp> (raw)
In-Reply-To: <201811070036.wA70a07Z025844@ccmail04.silk.ntt-tx.co.jp>
> Hello Yasufumi-san,
>
> My suggestion is to apply the first patch soon
> because without that patch, compile of spp encounters error.
> Soon is better.
If you compile SPP with DPDK v18.08, yes.
>
> About replacing deprecaed functions, I am planning to provide patch
> after the above mentioned patch applied to master.
Could you describe about your patch if you will update to v18.08? I think your patch is for replacing deprecated DPDK's APIs and
your patch(es) is applied even if my patch is not applied before (of course, need both of patches for compiling). Anyway, you
can send your patch anytime for reviewing.
Thanks,
>
> BR,
> Hideyuki Yamashita
> NTT TechnoCross
>
>> Hi Hideyuki,
>>
>> Could you tell me what is the point of your suggestion?
>>
>> I agreed not to disable warning option in Makefile and need to update for DPDK v18.08 by replacing deprecated functions. I think it is still required to remove deprecated `txq_flags` if update to v18.08. However, I am not sure if you suggest to apply the first patch soon, or it is OK later.
>>
>> Thanks,
>> Yasufumi
>>
>>> Hello,
>>>
>>> So far, it looks both patches are not merged into master branch.
>>> I think change on makefile is tentative one and no need to merge.
>>> But the other change on shared needs to be merged to master
>>> because it is essentical change.
>>>
>>> BR,
>>> Hideyuki Yamashita
>>> NTT TechnoCross
>>>
>>>> From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
>>>>
>>>> Compiling SPP with DPDK v18.08 causes some of erros and warnings
>>>> because of following reasons. This series of patches is to fix them.
>>>>
>>>> * Tx queue configuration is not updated for the new Tx offload API.
>>>>
>>>> * rte_eth_dev_attach/detach is deprecated but still remained.
>>>>
>>>> Yasufumi Ogawa (2):
>>>> shared: remove nouse txq_flags
>>>> makefile: ignore deprecated declarations
>>>>
>>>> src/nfv/Makefile | 1 +
>>>> src/shared/common.c | 1 -
>>>> src/vf/Makefile | 1 +
>>>> src/vm/Makefile | 1 +
>>>> 4 files changed, 3 insertions(+), 1 deletion(-)
>>>>
>>>> --
>>>> 2.7.4
next prev parent reply other threads:[~2018-11-07 3:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 10:54 [spp] " ogawa.yasufumi
2018-08-23 10:54 ` [spp] [PATCH 1/2] shared: remove nouse txq_flags ogawa.yasufumi
2018-08-23 10:54 ` [spp] [PATCH 2/2] makefile: ignore deprecated declarations ogawa.yasufumi
2018-11-06 11:18 ` [spp] [spp 03234] [PATCH 0/2] Fix compile error with DPDK v18.08 Hideyuki Yamashita
2018-11-06 11:37 ` [spp] Cannnot add pcap PMD and null PMD via spp.py Hideyuki Yamashita
2018-11-07 3:09 ` Yasufumi Ogawa
2018-11-06 12:26 ` [spp] [spp 03234] [PATCH 0/2] Fix compile error with DPDK v18.08 Yasufumi Ogawa
2018-11-07 0:35 ` Hideyuki Yamashita
2018-11-07 3:03 ` Yasufumi Ogawa [this message]
2018-11-07 3:30 ` [spp] [spp 03509] " Hideyuki Yamashita
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=b7586534-1679-9642-f367-61d3e9f184ea@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=spp@dpdk.org \
--cc=yamashita.hideyuki@po.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).