From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-spp <spp@dpdk.org>
Subject: Re: [spp] DPDK v18.08 support
Date: Mon, 27 Aug 2018 19:59:44 +0900 [thread overview]
Message-ID: <737dddd6-fbc5-0bc8-11fb-97c4e30908e2@lab.ntt.co.jp> (raw)
In-Reply-To: <80bb0dbe-04f1-503d-95e2-5cc37033a524@intel.com>
> On 8/23/2018 2:58 AM, Yasufumi Ogawa wrote:
>>> Hi Yasufumi,
>>>
>>> I am sure you already aware but for the record for mail list, latest spp doesn't
>>> compile with latest DPDK v18.08 release because of some deprecated fields and APIs.
>>>
>>> Do you guys already have a plan for the DPDK v18.08 support?
>> Hi Ferruh,
>>
>> Yes. I should replace deprecated rte_eth_dev_attach/detach() with rte_eal_hotplug_add/remove(). I have learned how to use this
>> new APIs and will send patches to make the changes.
>>
>> At first, I would like to add 'CFLAGS += -Wno-deprecated-declarations' option to avoid the problem similar to DPDK, then change
>> to new APIs.
>
> That would work but I am not sure how good idea it is.
> Deprecated deprecation is notify you to update your application, I think we
> shouldn't suppress these warnings.
OK. I would like to try to fix with new APIs. I already sent patches for the issue and I will send next patches as version 2.
Thanks for your comment.
Yasufumi
>
>>
>> Thanks,
>> Yasufumi
>>>
>>>
>>> Thanks,
>>> ferruh
>>>
>>
prev parent reply other threads:[~2018-08-27 11:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 13:04 Ferruh Yigit
2018-08-23 1:58 ` Yasufumi Ogawa
2018-08-24 9:22 ` Ferruh Yigit
2018-08-27 10:59 ` Yasufumi Ogawa [this message]
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=737dddd6-fbc5-0bc8-11fb-97c4e30908e2@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=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).