From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw(86313) [v14, 11/11] examples/l3fwd-power: enable PMD power mgmt
Date: 12 Jan 2021 01:38:39 -0800 [thread overview]
Message-ID: <93cfb9$h154g9@fmsmga005-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 884 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/86313
_apply issues_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: 2021-01-11 14:35:56
Reply_mail: 53f23eef1e34fb5677c140b62a1d5ce22f08b09a.1610375528.git.anatoly.burakov@intel.com
DPDK git baseline:
Repo:dpdk, CommitID: b1fd151267e6791a7649090c185413293549d033
* Repo: dpdk
Falling back to patching base and 3-way merge...
Auto-merging lib/librte_eal/version.map
CONFLICT (content): Merge conflict in lib/librte_eal/version.map
error: Failed to merge in the changes.
Patch failed at 0001 eal: uninline power intrinsics
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-01-12 9:38 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='93cfb9$h154g9@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).