From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2] devargs: fix policy check in rte_eal_devargs_add Date: Thu, 03 Aug 2017 21:36:47 +0200 Message-ID: <2003486.SEdAYn8PGO@xps> References: <1da8b8d0c80d7af97ca32c35a0215f99ad2f6666.1501693240.git.gaetan.rivet@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Gaetan Rivet Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 4D6622C16 for ; Thu, 3 Aug 2017 21:36:49 +0200 (CEST) In-Reply-To: <1da8b8d0c80d7af97ca32c35a0215f99ad2f6666.1501693240.git.gaetan.rivet@6wind.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" 02/08/2017 19:12, Gaetan Rivet: > Do not fail upon detecting a set bus configuration when adding an > rte_devargs. i.e. adding a blacklisted PCI device while the bus is > configured in whitelist mode. > > This failure condition has been introduced when the bus policies > were implemented. This implementation however was meant to strictly > follow the existing API. This check was not and should not be performed > until the current API has been properly deprecated. > > Fixes: 02823c1db0bc ("devargs: parse bus policies") > > Signed-off-by: Gaetan Rivet Adding a precision: The same kind of check is already done when parsing EAL options. Applied, thanks