DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: stable@dpdk.org, dev@dpdk.org, shreyansh.jain@nxp.com,
	hemant.agrawal@nxp.com
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] fslmc: don't log error for other devices
Date: Mon, 25 Feb 2019 16:23:38 +0100	[thread overview]
Message-ID: <3192751.N4LoNDf9Js@xps> (raw)
In-Reply-To: <20190206220414.9450-1-stephen@networkplumber.org>

+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 <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;
>  	}
>  
> 

      parent reply	other threads:[~2019-02-25 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 22:04 [dpdk-dev] " Stephen Hemminger
2019-02-06 22:10 ` [dpdk-dev] [PATCH] fslmc: remove unneeded strdup Stephen Hemminger
2019-02-25 15:23 ` Thomas Monjalon [this message]

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=3192751.N4LoNDf9Js@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=shreyansh.jain@nxp.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    /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).