From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw107351 [PATCH] eal/linux: fix fail to stop device monitor error
Date: Fri, 11 Feb 2022 02:28:09 -0500 (EST) [thread overview]
Message-ID: <20220211072809.955A9A76D@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/107351
_apply patch failure_
Submitter: Wenxuan wu <wenxuanx.wu@intel.com>
Date: Friday, February 11 2022 06:53:15
Applied on: CommitID:1d1126ad436e8c7c015fb3f67ad3af05c3b397d5
Apply patch set 107351 failed:
Checking patch lib/eal/linux/eal_dev.c...
error: while searching for:
if (!monitor_refcount) {
RTE_LOG(ERR, EAL, "device event monitor already stopped\n");
goto exit;
}
error: patch failed: lib/eal/linux/eal_dev.c:366
error: while searching for:
RTE_LOG(ERR, EAL, "fail to unregister uevent callback.\n");
goto exit;
}
close(rte_intr_fd_get(intr_handle));
rte_intr_instance_free(intr_handle);
intr_handle = NULL;
error: patch failed: lib/eal/linux/eal_dev.c:381
Applying patch lib/eal/linux/eal_dev.c with 2 rejects...
Rejected hunk #1.
Rejected hunk #2.
diff a/lib/eal/linux/eal_dev.c b/lib/eal/linux/eal_dev.c (rejected hunks)
@@ -366,7 +366,7 @@ rte_dev_event_monitor_stop(void)
if (!monitor_refcount) {
RTE_LOG(ERR, EAL, "device event monitor already stopped\n");
-
+
goto exit;
}
@@ -381,7 +381,7 @@ rte_dev_event_monitor_stop(void)
RTE_LOG(ERR, EAL, "fail to unregister uevent callback.\n");
goto exit;
}
-
+
close(rte_intr_fd_get(intr_handle));
rte_intr_instance_free(intr_handle);
intr_handle = NULL;
https://lab.dpdk.org/results/dashboard/patchsets/21028/
UNH-IOL DPDK Community Lab
next reply other threads:[~2022-02-11 7:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 7:28 dpdklab [this message]
[not found] <20220211065315.66814-1-wenxuanx.wu@intel.com>
2022-02-11 7:14 ` checkpatch
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=20220211072809.955A9A76D@noxus.dpdklab.iol.unh.edu \
--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).