From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw106155 [PATCH] [v5] raw/ifpga: fix pthread cannot join
Date: Thu, 20 Jan 2022 22:48:35 -0500 (EST) [thread overview]
Message-ID: <20220121034835.23F666DE2@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/106155
_apply patch failure_
Submitter: Wei Huang <wei.huang@intel.com>
Date: Friday, January 21 2022 03:32:46
Applied on: CommitID:9cc217a28310d21fba56e5eceb740b4feb7e0949
Apply patch set 106155 failed:
Checking patch drivers/raw/ifpga/ifpga_rawdev.c...
error: while searching for:
"Fail to create ifpga nonitor thread");
return -1;
}
ifpga_monitor_start = 1;
}
return 0;
error: patch failed: drivers/raw/ifpga/ifpga_rawdev.c:534
Applying patch drivers/raw/ifpga/ifpga_rawdev.c with 1 reject...
Hunk #1 applied cleanly.
Hunk #2 applied cleanly.
Hunk #3 applied cleanly.
Rejected hunk #4.
Hunk #5 applied cleanly.
Hunk #6 applied cleanly.
diff a/drivers/raw/ifpga/ifpga_rawdev.c b/drivers/raw/ifpga/ifpga_rawdev.c (rejected hunks)
@@ -534,7 +534,7 @@ static int set_surprise_link_check_aer(
"Fail to create ifpga nonitor thread");
return -1;
}
- ifpga_monitor_start = 1;
+ rte_atomic32_set(&ifpga_monitor_start, 1);
}
return 0;
https://lab.dpdk.org/results/dashboard/patchsets/20757/
UNH-IOL DPDK Community Lab
next reply other threads:[~2022-01-21 3:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 3:48 dpdklab [this message]
[not found] <20220121033246.10339-1-wei.huang@intel.com>
2022-01-21 3:37 ` |WARNING| pw106155 [PATCH v5] " 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=20220121034835.23F666DE2@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).