From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw127282-127283 [PATCH] [2/2] event/cnxk: honor event limit set by config
Date: Wed, 24 May 2023 02:10:13 -0700 (PDT) [thread overview]
Message-ID: <646dd475.620a0220.65d13.1bd7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/127282
_apply patch failure_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Wednesday, May 24 2023 08:52:33
Applied on: CommitID:c41a103c961ded5a0966652f4daf0a661a947352
Apply patch set 127282-127283 failed:
Checking patch drivers/event/cnxk/cnxk_eventdev.c...
Hunk #2 succeeded at 192 (offset -1 lines).
Checking patch drivers/event/cnxk/cnxk_eventdev.h...
error: while searching for:
uint32_t min_dequeue_timeout_ns;
uint32_t max_dequeue_timeout_ns;
int32_t max_num_events;
uint64_t xaq_lmt;
int64_t *fc_cache_space;
rte_iova_t fc_iova;
error: patch failed: drivers/event/cnxk/cnxk_eventdev.h:89
Applied patch drivers/event/cnxk/cnxk_eventdev.c cleanly.
Applying patch drivers/event/cnxk/cnxk_eventdev.h with 1 reject...
Rejected hunk #1.
hint: Use 'git am --show-current-patch' to see the failed patch
diff a/drivers/event/cnxk/cnxk_eventdev.h b/drivers/event/cnxk/cnxk_eventdev.h (rejected hunks)
@@ -89,6 +89,7 @@ struct cnxk_sso_evdev {
uint32_t min_dequeue_timeout_ns;
uint32_t max_dequeue_timeout_ns;
int32_t max_num_events;
+ int32_t num_events;
uint64_t xaq_lmt;
int64_t *fc_cache_space;
rte_iova_t fc_iova;
https://lab.dpdk.org/results/dashboard/patchsets/26362/
UNH-IOL DPDK Community Lab
reply other threads:[~2023-05-24 9:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=646dd475.620a0220.65d13.1bd7SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@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).