From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |WARNING| pw(94533) sid(17403) [6/6] Allow choice between internal EAL thread API and external lib
Date: 18 Jun 2021 15:02:56 -0700 [thread overview]
Message-ID: <dd034b$j34o8h@fmsmga005-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/94533
_apply issues_
Submitter: Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>
Date: 2021-06-18 21:54:54
Reply_mail: 1624053294-31255-7-git-send-email-navasile@linux.microsoft.com
DPDK git baseline:
Repo:dpdk, CommitID: 8050b61562723c531ad9d4736f5549050eba190e
* Repo: dpdk
Starting new HTTP connection (1): proxy-shz.intel.com
Starting new HTTP connection (1): proxy-shz.intel.com
error: lib/eal/common/rte_thread.c: does not exist in index
error: patch failed: lib/eal/include/rte_thread.h:24
error: lib/eal/include/rte_thread.h: patch does not apply
error: patch failed: lib/eal/version.map:443
error: lib/eal/version.map: patch does not apply
error: patch failed: lib/eal/windows/rte_thread.c:556
error: lib/eal/windows/rte_thread.c: patch does not apply
Applying: eal: add function that sets thread name
Patch failed at 0001 eal: add function that sets thread name
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
DPDK STV team
reply other threads:[~2021-06-18 22:02 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='dd034b$j34o8h@fmsmga005-auth.fm.intel.com' \
--to=sys_stv@intel.com \
--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).