From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: dev@dpdk.org, ferruh.yigit@intel.com
Subject: [dpdk-dev] [PATCH 2/3] bus/fslmc: fix to remove err print for non-fslmc devices
Date: Mon, 22 Jul 2019 12:24:06 +0530 [thread overview]
Message-ID: <20190722065407.9180-2-hemant.agrawal@nxp.com> (raw)
In-Reply-To: <20190722065407.9180-1-hemant.agrawal@nxp.com>
This patch removes the unneccessary err prints when using
non-dpaa2 devices.
Fixes: e67a61614d0b ("bus/fslmc: support device iteration")
Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
---
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 9e4146aba..a2f482516 100644
--- a/drivers/bus/fslmc/fslmc_bus.c
+++ b/drivers/bus/fslmc/fslmc_bus.c
@@ -601,7 +601,7 @@ fslmc_bus_dev_iterate(const void *start, const char *str,
/* Expectation is that device would be name=device_name */
if (strncmp(str, "name=", 5) != 0) {
- DPAA2_BUS_ERR("Invalid device string (%s)\n", str);
+ DPAA2_BUS_DEBUG("Invalid device string (%s)\n", str);
return NULL;
}
--
2.17.1
next prev parent reply other threads:[~2019-07-22 6:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 6:54 [dpdk-dev] [PATCH 1/3] bus/dpaa: fix to remove err print for non-dpaa devices Hemant Agrawal
2019-07-22 6:54 ` Hemant Agrawal [this message]
2019-07-22 6:54 ` [dpdk-dev] [PATCH 3/3] bus/fslmc: fix the compliation err with ppc64 compiler Hemant Agrawal
2019-07-22 8:16 ` Thomas Monjalon
2019-07-22 10:03 ` [dpdk-dev] [PATCH v2 1/3] bus/dpaa: fix to remove err print for non-dpaa devices Hemant Agrawal
2019-07-22 10:03 ` [dpdk-dev] [PATCH v2 2/3] bus/fslmc: fix to remove err print for non-fslmc devices Hemant Agrawal
2019-07-22 10:03 ` [dpdk-dev] [PATCH v2 3/3] bus/fslmc: fix the compliation err with ppc64 compiler Hemant Agrawal
2019-07-22 14:14 ` [dpdk-dev] [PATCH v2 1/3] bus/dpaa: fix to remove err print for non-dpaa devices Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190722065407.9180-2-hemant.agrawal@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.