From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH] ethdev: filter destroy event before probed Date: Thu, 25 Oct 2018 13:47:06 +0100 Message-ID: <44bf0aeb-dbb7-5a7b-31da-238f2c464bbf@intel.com> References: <20181024131232.6146-1-thomas@monjalon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Thomas Monjalon , Andrew Rybchenko Return-path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 67961559A for ; Thu, 25 Oct 2018 14:47:09 +0200 (CEST) In-Reply-To: Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 10/25/2018 1:38 PM, Ferruh Yigit wrote: > On 10/24/2018 2:12 PM, Thomas Monjalon wrote: >> If a port is being created and rollbacked because of an error, >> the event RTE_ETH_EVENT_DESTROY should not be sent. >> It makes no sense to receive a destroy event for a port which >> was not yet announced via RTE_ETH_EVENT_NEW. >> >> Signed-off-by: Thomas Monjalon > > Reviewed-by: Ferruh Yigit Applied to dpdk-next-net/master, thanks.