From: "Zhao, MeijuanX" <meijuanx.zhao@intel.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"Wu, ChangqingX" <changqingx.wu@intel.com>
Subject: Re: [dpdk-dev] [PATCH] eal/bsd: silence not supported error in interrupts
Date: Fri, 3 Aug 2018 01:54:12 +0000 [thread overview]
Message-ID: <9866F1E5CE768A45B24F6603C6EF54DE01414C2B@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <7679658279b52ae069260b62696398a97648eb6a.1532679585.git.anatoly.burakov@intel.com>
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Anatoly Burakov
Sent: Friday, July 27, 2018 4:25 PM
To: dev@dpdk.org
Cc: Richardson, Bruce <bruce.richardson@intel.com>; thomas@monjalon.net; Wu, ChangqingX <changqingx.wu@intel.com>
Subject: [dpdk-dev] [PATCH] eal/bsd: silence not supported error in interrupts
Currently, nic_uio driver does not support interrupts, so any attempts to install an interrupt handler will fail with a not supported error, which will cause an error message that is confusing to the user.
Silence this error by moving it to debug log level, and reword the message to avoid containing the word "Error", to avoid triggering DTS test failures [1].
[1] https://git.dpdk.org/tools/dts/tree/tests/
TestSuite_scatter.py?#n110
Fixes: 23150bd8d8a8 ("eal/bsd: add interrupt thread")
Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
Tested-by: Wu, ChangqingX <changqingx.wu@intel.com>
prev parent reply other threads:[~2018-08-03 1:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 8:24 Anatoly Burakov
2018-08-01 15:54 ` Thomas Monjalon
2018-08-03 1:54 ` Zhao, MeijuanX [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=9866F1E5CE768A45B24F6603C6EF54DE01414C2B@shsmsx102.ccr.corp.intel.com \
--to=meijuanx.zhao@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=changqingx.wu@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).