From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id D20F34C6C; Mon, 25 Feb 2019 16:23:41 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 458E12076C; Mon, 25 Feb 2019 10:23:41 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 25 Feb 2019 10:23:41 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=Y0Gl4iN00hkaQjomf+O6H8tITHuv7F6pHOvy6JS2SRY=; b=dUhbu/zI0dnF S3yL54iruHTZ+NEVy0MNDs/+UXp3KNcZpmMFAWu6rKrDn6E0LFv+2au/SSLtRIqy I6wyoEPQqf9KtJ72GD9BlFNaiAt9OOfOUZrGHk1VXc7MrtMTY+Js9W+g+zxNOIm4 TFKy1q1QI3Mzxe3hsqnAWYWsEJ5ussI= 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=Y0Gl4iN00hkaQjomf+O6H8tITHuv7F6pHOvy6JS2S RY=; b=MVrQxFugAOYexkbEmnhGr/8VQCu4wnh83Jv5XuwHL8CocC1aUmLYRmlO/ v461mJRHntUkD2IRW0UwkcKaU4UXGZuVvHT0QQpkPjwObzx9oXXVHiZNdrne+D6s U94tnkexnFDHquAasWrH5eJa3NDUn/Ty8CD6m8GP2GM4nqJArP5mp3m95eiAiTaW GuMCLkwV3XolDBSj8Dd4j54y4rtCPvhGmlh6byJKASRtCZThjwp5W+BH3fMG/vhm p8vdIPCDYxmxdxJOPvJX84QRSaXs0xNJvyOlJ7QaOC0W4qKWDkHt/bX20gLHcnVT kkTtmCNu9n7O9o9N6UqRn0GXxAt/w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrudejgdejkeculddtuddrgedtledrtddtmd cutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 055D9E4599; Mon, 25 Feb 2019 10:23:39 -0500 (EST) From: Thomas Monjalon To: Stephen Hemminger Cc: stable@dpdk.org, dev@dpdk.org, shreyansh.jain@nxp.com, hemant.agrawal@nxp.com Date: Mon, 25 Feb 2019 16:23:38 +0100 Message-ID: <3192751.N4LoNDf9Js@xps> In-Reply-To: <20190206220414.9450-1-stephen@networkplumber.org> References: <20190206220414.9450-1-stephen@networkplumber.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] fslmc: don't log error for other devices X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2019 15:23:42 -0000 +Cc maintainers 06/02/2019 23:04, Stephen Hemminger: > When fslmc is built as part of a general distribution, the > bus code will log errors when other devices are present. > > This could confuse users it is not an error. > > Fixes: 50245be05d1a ("bus/fslmc: support device blacklisting") > Signed-off-by: Stephen Hemminger > --- > drivers/bus/fslmc/fslmc_bus.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/bus/fslmc/fslmc_bus.c b/drivers/bus/fslmc/fslmc_bus.c > index 44c0827ced0b..a2525780cd08 100644 > --- a/drivers/bus/fslmc/fslmc_bus.c > +++ b/drivers/bus/fslmc/fslmc_bus.c > @@ -249,7 +249,7 @@ rte_fslmc_parse(const char *name, void *addr) > strncmp("dpmcp", t_ptr, 5) && > strncmp("dpdmai", t_ptr, 6) && > strncmp("dpdmux", t_ptr, 6)) { > - DPAA2_BUS_ERR("Unknown or unsupported device"); > + DPAA2_BUS_DEBUG("Unknown or unsupported device (%s)", name); > goto err_out; > } > >