Soft Patch Panel
 help / color / mirror / Atom feed
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
To: x-fn-spp@sl.ntt-tx.co.jp
Cc: ferruh.yigit@intel.com, spp@dpdk.org
Subject: Re: [spp] [PATCH 0/6] Replace deprecated APIs
Date: Fri, 9 Nov 2018 12:34:47 +0900	[thread overview]
Message-ID: <ce719551-d410-294b-6983-6f6dbe5cd7f7@lab.ntt.co.jp> (raw)
In-Reply-To: <201811070507.wA757WWo008866@imss03.silk.ntt-tx.co.jp>

On 2018/11/07 14:07, x-fn-spp@sl.ntt-tx.co.jp wrote:
> From: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
> 
>>From DPDK-18.08, the follwing APIs become deprecated and 
> will be deleted in DPDK18.08.
> - rte_eth_dev_attach()
> - rte_eth_dev_detach()
> 
> For rte_eth_dev_attach(), use of rte_eal_hotplug_add() is recommended.
> For rte_eth_dev_detach(), use of rte_eal_hotplug_remove() is recommended.
> 
> To follow the above changes, this patch set provides replacement of
> those APIs.
Hideyuki,

Thank you for suggesting to update to v18.08!

Could you re-consider the name of function you added by referring conventions of DPDK and SPP? It has almost no means if just 
`attach` or `detach`. It is preferable to be self explanatory for how your function works.

Commit messages are also required to be revised. Update for the change of function name and modify invalid descriptions for 
documentation guidelines.

Thanks
> 
> Signed-off-by: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
> Signed-off-by: Naoki Takada <takada.naoki@lab.ntt.co.jp>
> 
> Hideyuki Yamashita (6):
>    shared: addition of attach()
>    spp_nfv: replacement of rte_eth_dev_attach()
>    spp_vf:replacement of rte_eth_dev_attach()
>    shared: addition of detach()
>    spp_nfv: replacement of rte_eth_dev_detach()
>    spp_vm: replacement of rte_eth_dev_detach().
> 
>   src/nfv/nfv.c       | 12 ++++-----
>   src/shared/common.c | 64 +++++++++++++++++++++++++++++++++++++++++++++
>   src/shared/common.h | 32 +++++++++++++++++++++++
>   src/vf/spp_vf.c     |  4 +--
>   src/vm/main.c       |  2 +-
>   5 files changed, 105 insertions(+), 9 deletions(-)
> 


-- 
Yasufumi Ogawa
NTT Network Service Systems Labs

  reply	other threads:[~2018-11-09  3:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07  5:07 x-fn-spp
2018-11-09  3:34 ` Yasufumi Ogawa [this message]
2018-11-09  9:22   ` [spp] [spp 03539] " Hideyuki Yamashita
2018-11-12 11:15     ` Yasufumi Ogawa
2018-11-13  0:27       ` Hideyuki Yamashita
2018-11-13  8:22         ` Yasufumi Ogawa
2018-11-14  0:40           ` Hideyuki Yamashita
2018-11-15  0:16             ` Nakamura Hioryuki
2018-11-15 14:17               ` Yasufumi Ogawa
2018-11-21  6:52 ` [spp] [PATCH v2 " x-fn-spp
2018-11-24 12:57   ` Yasufumi Ogawa
2018-11-28  2:44   ` Yasufumi Ogawa
2018-11-21  6:52 ` [spp] [PATCH v2 1/6] shared: add dev_attach_by_devargs x-fn-spp
2018-11-24 14:54   ` Yasufumi Ogawa
2018-11-26  4:12     ` [spp] [spp 03664] " Hideyuki Yamashita
2018-11-21  6:52 ` [spp] [PATCH v2 2/6] spp_nfv: replace deprecated rte_eth_dev_attach x-fn-spp
2018-11-21  6:52 ` [spp] [PATCH v2 3/6] spp_vf: " x-fn-spp
2018-11-21  6:52 ` [spp] [PATCH v2 4/6] shared: add dev_detach_by_port_id x-fn-spp
2018-11-24 15:02   ` Yasufumi Ogawa
2018-11-21  6:52 ` [spp] [PATCH v2 5/6] spp_nfv: replace deprecated rte_eth_dev_detach x-fn-spp
2018-11-21  6:52 ` [spp] [PATCH v2 6/6] spp_vm: " x-fn-spp

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=ce719551-d410-294b-6983-6f6dbe5cd7f7@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).