From: Stephen Hemminger <stephen@networkplumber.org>
To: hemant.agrawal@nxp.com, shreyansh.jain@nxp.com
Cc: dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH v2 1/2] bus/fslmc: don't log error for other devices
Date: Tue, 12 Mar 2019 10:11:51 -0700 [thread overview]
Message-ID: <20190312171152.28637-2-stephen@networkplumber.org> (raw)
In-Reply-To: <20190312171152.28637-1-stephen@networkplumber.org>
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 <stephen@networkplumber.org>
---
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;
}
--
2.17.1
next prev parent reply other threads:[~2019-03-12 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 17:11 [dpdk-dev] [PATCH v2 0/2] bus/fslmc: logging fixes Stephen Hemminger
2019-03-12 17:11 ` Stephen Hemminger [this message]
2019-03-13 13:59 ` [dpdk-dev] [PATCH v2 1/2] bus/fslmc: don't log error for other devices Hemant Agrawal
[not found] ` <CGME20190314145248eucas1p118322756bdfe01ea81a9a4417e05633e@eucas1p1.samsung.com>
2019-03-14 14:52 ` Ilya Maximets
2019-03-14 14:52 ` Ilya Maximets
2019-03-12 17:11 ` [dpdk-dev] [PATCH v2 2/2] bus/fslmc: remove unneeded strdup Stephen Hemminger
2019-03-13 14:00 ` Hemant Agrawal
2019-03-29 13:00 ` [dpdk-dev] [PATCH v2 0/2] bus/fslmc: logging fixes Thomas Monjalon
2019-03-29 13:00 ` 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=20190312171152.28637-2-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=shreyansh.jain@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).