From: Ilya Maximets <i.maximets@samsung.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
hemant.agrawal@nxp.com, shreyansh.jain@nxp.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 1/2] bus/fslmc: don't log error for other devices
Date: Thu, 14 Mar 2019 17:52:47 +0300 [thread overview]
Message-ID: <7443e255-9db6-fa14-9faa-2351eb556196@samsung.com> (raw)
Message-ID: <20190314145247.zHUAev7LTsIPTHfpgczHDKPwHg8hWTN1Svs1KbtIoC0@z> (raw)
In-Reply-To: <20190312171152.28637-2-stephen@networkplumber.org>
On 12.03.2019 20:11, Stephen Hemminger wrote:
> 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>
> ---
These error messages are annoying. Thanks for fixing!
Acked-by: Ilya Maximets <i.maximets@samsung.com>
next prev parent reply other threads:[~2019-03-14 14:52 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 ` [dpdk-dev] [PATCH v2 1/2] bus/fslmc: don't log error for other devices Stephen Hemminger
2019-03-13 13:59 ` Hemant Agrawal
[not found] ` <CGME20190314145248eucas1p118322756bdfe01ea81a9a4417e05633e@eucas1p1.samsung.com>
2019-03-14 14:52 ` Ilya Maximets [this message]
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=7443e255-9db6-fa14-9faa-2351eb556196@samsung.com \
--to=i.maximets@samsung.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=shreyansh.jain@nxp.com \
--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).