From: "Xu, Rosen" <rosen.xu@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
"Zhang, Tianfei" <tianfei.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Thomas Monjalon <thomas@monjalon.net>,
"Stokes, Ian" <ian.stokes@intel.com>
Subject: Re: [dpdk-dev] [PATCH] eal: remove experimental from hotplug add/remove
Date: Mon, 8 Oct 2018 02:58:25 +0000 [thread overview]
Message-ID: <0E78D399C70DA940A335608C6ED296D73A2D0D86@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <0bf1f985-3575-0fa9-252b-1e3654ea2f19@intel.com>
> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Tuesday, October 02, 2018 18:24
> To: Andrew Rybchenko <arybchenko@solarflare.com>; Xu, Rosen
> <rosen.xu@intel.com>; Zhang, Tianfei <tianfei.zhang@intel.com>
> Cc: dev@dpdk.org; Thomas Monjalon <thomas@monjalon.net>; Stokes, Ian
> <ian.stokes@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] eal: remove experimental from hotplug
> add/remove
>
> On 10/2/2018 11:08 AM, Andrew Rybchenko wrote:
> > On 10/2/18 2:04 PM, Ferruh Yigit wrote:
> >> rte_eal_hotplug_add() & rte_eal_hotplug_remove() APIs first added on
> >> v17.08 as experimental
> >> Commit a3ee360f4440 ("eal: add hotplug add/remove device")
> >>
> >> When __rte_experimental tag created, APIs tagged with it on v18.02
> >> Commit 77b7b81e32e9 ("add experimental tag to appropriate functions")
> >>
> >> After rte_eth_dev_attach() & rte_eth_dev_detach() APIs has been
> >> deprecated in v18.08 eal APIs are only ones for hotplug operations
> >> Commit 9f2be5b3db8b ("ethdev: deprecate attach and detach functions")
> >>
> >> These APIs are around for a few releases now and without an
> >> alternative, removing the experimental tag from them.
> >>
> >> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> >
> > Dup of http://patches.dpdk.org/patch/45791/ ?
>
> Ahh, yes it is, I will mark this as Rejected, thanks.
Just back from holiday, a long story of this patch and 45791 :)
prev parent reply other threads:[~2018-10-08 2:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 11:04 Ferruh Yigit
2018-10-02 10:08 ` Andrew Rybchenko
2018-10-02 10:23 ` Ferruh Yigit
2018-10-08 2:58 ` Xu, Rosen [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=0E78D399C70DA940A335608C6ED296D73A2D0D86@SHSMSX104.ccr.corp.intel.com \
--to=rosen.xu@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ian.stokes@intel.com \
--cc=thomas@monjalon.net \
--cc=tianfei.zhang@intel.com \
/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).