From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 5886AA0096 for ; Wed, 10 Apr 2019 18:45:43 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 4CB5F1B105; Wed, 10 Apr 2019 18:45:43 +0200 (CEST) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id EA2D51B131 for ; Wed, 10 Apr 2019 18:45:41 +0200 (CEST) Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 5535A6DDCA; Wed, 10 Apr 2019 16:45:41 +0000 (UTC) Received: from rh.redhat.com (ovpn-117-94.ams2.redhat.com [10.36.117.94]) by smtp.corp.redhat.com (Postfix) with ESMTP id 14CC25D962; Wed, 10 Apr 2019 16:45:39 +0000 (UTC) From: Kevin Traynor To: Thomas Monjalon Cc: Rami Rosen , Andrew Rybchenko , dpdk stable Date: Wed, 10 Apr 2019 17:43:54 +0100 Message-Id: <20190410164411.10546-46-ktraynor@redhat.com> In-Reply-To: <20190410164411.10546-1-ktraynor@redhat.com> References: <20190410164411.10546-1-ktraynor@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.28]); Wed, 10 Apr 2019 16:45:41 +0000 (UTC) Subject: [dpdk-stable] patch 'bus/vdev: fix debug message on probing' has been queued to LTS release 18.11.2 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: , Errors-To: stable-bounces@dpdk.org Sender: "stable" Hi, FYI, your patch has been queued to LTS release 18.11.2 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 04/16/19. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. This will indicate if there was any rebasing needed to apply to the stable branch. If there were code changes for rebasing (ie: not only metadata diffs), please double check that the rebase was correctly done. Thanks. Kevin Traynor --- >From 7d591e5568119f2856e41a1164fe42ba61aed56c Mon Sep 17 00:00:00 2001 From: Thomas Monjalon Date: Thu, 21 Feb 2019 20:01:24 +0100 Subject: [PATCH] bus/vdev: fix debug message on probing [ upstream commit 4169ed6ed1c31b75f070cdccf3ee82561d4b79ce ] The log was printing the device name two times, first one being supposed to be the driver name. As we don't know yet the driver name, the log is simplified. Fixes: 9bf4901d1a11 ("bus/vdev: remove probe with driver name option") Signed-off-by: Thomas Monjalon Reviewed-by: Rami Rosen Reviewed-by: Andrew Rybchenko --- drivers/bus/vdev/vdev.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/bus/vdev/vdev.c b/drivers/bus/vdev/vdev.c index 2c03ca418..722541179 100644 --- a/drivers/bus/vdev/vdev.c +++ b/drivers/bus/vdev/vdev.c @@ -145,7 +145,5 @@ vdev_probe_all_drivers(struct rte_vdev_device *dev) name = rte_vdev_device_name(dev); - - VDEV_LOG(DEBUG, "Search driver %s to probe device %s", name, - rte_vdev_device_name(dev)); + VDEV_LOG(DEBUG, "Search driver to probe device %s", name); if (vdev_parse(name, &driver)) -- 2.20.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2019-04-10 14:06:11.418649236 +0100 +++ 0046-bus-vdev-fix-debug-message-on-probing.patch 2019-04-10 14:06:07.985291473 +0100 @@ -1,14 +1,15 @@ -From 4169ed6ed1c31b75f070cdccf3ee82561d4b79ce Mon Sep 17 00:00:00 2001 +From 7d591e5568119f2856e41a1164fe42ba61aed56c Mon Sep 17 00:00:00 2001 From: Thomas Monjalon Date: Thu, 21 Feb 2019 20:01:24 +0100 Subject: [PATCH] bus/vdev: fix debug message on probing +[ upstream commit 4169ed6ed1c31b75f070cdccf3ee82561d4b79ce ] + The log was printing the device name two times, first one being supposed to be the driver name. As we don't know yet the driver name, the log is simplified. Fixes: 9bf4901d1a11 ("bus/vdev: remove probe with driver name option") -Cc: stable@dpdk.org Signed-off-by: Thomas Monjalon Reviewed-by: Rami Rosen