From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: [PATCH v2] doc: update ethdev APIs to return named opaque type Date: Fri, 9 Feb 2018 10:18:18 +0000 Message-ID: <20180209101818.70041-1-ferruh.yigit@intel.com> References: <20180209101119.69860-1-ferruh.yigit@intel.com> Cc: dev@dpdk.org, Ferruh Yigit , Konstantin Ananyev , Stephen Hemminger , Bruce Richardson , Thomas Monjalon To: Neil Horman , John McNamara , Marko Kovacevic Return-path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 85F121B84D for ; Fri, 9 Feb 2018 11:18:23 +0100 (CET) In-Reply-To: <20180209101119.69860-1-ferruh.yigit@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Ethdev APIs to add callback return the callback object as "void *", update return type to actual object type "struct rte_eth_rxtx_callback *" Signed-off-by: Ferruh Yigit --- Cc: Konstantin Ananyev Cc: Stephen Hemminger Cc: Bruce Richardson Cc: Thomas Monjalon --- doc/guides/rel_notes/deprecation.rst | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index bbd9456a7..5cb5a00d2 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -49,6 +49,13 @@ Deprecation Notices rte_eth_dev_get_sec_ctx() is using uint8_t for port_id, which should be uint16_t. +* ethdev: functions add rx/tx callback will return named opaque type + rte_eth_add_rx_callback(), rte_eth_add_first_rx_callback() and + rte_eth_add_tx_callback() functions currently return callback object as + "void \*" but APIs to delete callbacks get "struct rte_eth_rxtx_callback \*" + as parameter. For consistency functions adding callback will return + "struct rte_eth_rxtx_callback \*" instead of "void * ". + * i40e: The default flexible payload configuration which extracts the first 16 bytes of the payload for RSS will be deprecated starting from 18.02. If required the previous behavior can be configured using existing flow -- 2.14.3