From: <pbhagavatula@marvell.com>
To: <jerinj@marvell.com>
Cc: <dev@dpdk.org>, Pavan Nikhilesh <pbhagavatula@marvell.com>,
<stable@dpdk.org>
Subject: [PATCH] test/event: fix missing schedule type assignment
Date: Wed, 24 Jul 2024 01:02:12 +0530 [thread overview]
Message-ID: <20240723193212.2625-1-pbhagavatula@marvell.com> (raw)
From: Pavan Nikhilesh <pbhagavatula@marvell.com>
Missing schedule type assignment might set it to
incorrect value, set it to SCHED_TYPE_PARALLEL.
Fixes: d007a7f39de3 ("eventdev: introduce link profiles")
Cc: stable@dpdk.org
Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
---
app/test/test_eventdev.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/app/test/test_eventdev.c b/app/test/test_eventdev.c
index e4e234dc98..9a6c8f470c 100644
--- a/app/test/test_eventdev.c
+++ b/app/test/test_eventdev.c
@@ -1189,6 +1189,7 @@ test_eventdev_profile_switch(void)
ev.op = RTE_EVENT_OP_NEW;
ev.flow_id = 0;
ev.u64 = 0xBADF00D0;
+ ev.sched_type = RTE_SCHED_TYPE_PARALLEL;
rc = rte_event_enqueue_burst(TEST_DEV_ID, 0, &ev, 1);
TEST_ASSERT(rc == 1, "Failed to enqueue event");
ev.queue_id = 1;
--
2.25.1
next reply other threads:[~2024-07-23 19:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 19:32 pbhagavatula [this message]
2024-09-17 15:16 ` Jerin Jacob
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=20240723193212.2625-1-pbhagavatula@marvell.com \
--to=pbhagavatula@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=stable@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).