From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 9E4151B678; Wed, 9 May 2018 21:05:39 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 414B322ACB; Wed, 9 May 2018 15:05:39 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 09 May 2018 15:05:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=Kjn0nIVv8M/HmG34TSipsCPAhc 2UwKfMm6IAVbGk2yQ=; b=CpkF2yq6bgBPWajm9MV3wQ/8geRoOjMDu+KM5jmXyR ya6IO+9FRxaBGenkijzWTPaWpbBE1lh+Ny+ucI+x+TNwBB0AKRnoJcWNoVtsh5FT 0+DEnImF2QDlPJGJ0k4EtSwnyTDaV6jdoeZq+JTnEq0Onin6AUhwdbn1amM557Pt k= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=Kjn0nI Vv8M/HmG34TSipsCPAhc2UwKfMm6IAVbGk2yQ=; b=JxSUqKpTST1NWvONjNExki SwUlFQADM9PEkZyWIhacA29/gbU5uMk9/SawnGb1kuJS55kr4OI4B1PJhfASmnuZ yxE4twh1vLyPWNCCQ7nJf0vuBlNoPifXARVwFN015IVbWCFa2p9jxTBMZl1Ek6Ql wbIkKxTOkFuqSzQ0nlrC2vwxAcW1ry3d1Ovy1958AyyP9Q9pqgMT66DZ9KbrSZCG XiF7eG6bOwzdJ1uQTPo1ctPKBM64xmcc9M+Kw1P33Z2XJl25mOeVTu462VDdRFxh G1iwvuVTwuW4t5AAYn+/W4pvZglT6FWT+qig5Ydbkj0//C8lHB13Kw8/EGpNrr2Q == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 1F9ABE4FD2; Wed, 9 May 2018 15:05:38 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit Cc: dev@dpdk.org, Matan Azrad , stable@dpdk.org Date: Wed, 09 May 2018 21:05:36 +0200 Message-ID: <1724342.ZJg8p6OfUB@xps> In-Reply-To: References: <20180509094337.26112-1-thomas@monjalon.net> <20180509094337.26112-7-thomas@monjalon.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH 06/11] ethdev: allow ownership operations on unused port X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 May 2018 19:05:39 -0000 09/05/2018 20:00, Ferruh Yigit: > On 5/9/2018 10:43 AM, Thomas Monjalon wrote: > > From: Matan Azrad > > > > When the state will be updated later than in allocation, > > we may need to update the ownership of a port which is > > still in state unused. > > > > It will be used to take ownership of a port before it is > > declared as available for other entities. > > > > Cc: stable@dpdk.org > > > > Signed-off-by: Matan Azrad > > Acked-by: Thomas Monjalon > > Hi Thomas, > > If I remember correctly port ownership merged last release in last minute, > without much review. Now we are having these updates on it on rc3, not sure if > many people aware of this feature. The main purpose is about fixing events NEW and DESTROY. > Instead of getting these updates in rc3, any chance to postpone to next release > and do more reviews? They are not updates but fixes, I think we must consider them.