From: Qiming Yang <qiming.yang@intel.com>
To: dev@dpdk.org
Cc: Qiming Yang <qiming.yang@intel.com>
Subject: [dpdk-dev] [PATCH] test: fixed uncorrect interrupt type
Date: Sat, 17 Nov 2018 01:04:00 +0800 [thread overview]
Message-ID: <20181116170400.76667-1-qiming.yang@intel.com> (raw)
Fixed the interrupt type using error. Check valid alarm should use
TEST_INTERRUPT_HANDLE_VALID_ALARM.
Fixes: 493b8e173fe6 ("eal: add device event handle in interrupt thread")
Signed-off-by: Qiming Yang <qiming.yang@intel.com>
---
test/test/test_interrupts.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/test/test/test_interrupts.c b/test/test/test_interrupts.c
index dc19175..4e82e9a 100644
--- a/test/test/test_interrupts.c
+++ b/test/test/test_interrupts.c
@@ -424,7 +424,7 @@ test_interrupt(void)
printf("Check valid alarm interrupt full path\n");
if (test_interrupt_full_path_check(
- TEST_INTERRUPT_HANDLE_VALID_DEV_EVENT) < 0) {
+ TEST_INTERRUPT_HANDLE_VALID_ALARM) < 0) {
printf("failure occurred during checking valid alarm "
"interrupt full path\n");
goto out;
--
2.9.5
next reply other threads:[~2018-11-16 9:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 17:04 Qiming Yang [this message]
2018-11-18 22:10 ` 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=20181116170400.76667-1-qiming.yang@intel.com \
--to=qiming.yang@intel.com \
--cc=dev@dpdk.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).