From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw(79128) [v2, 4/4] net/ice: add devarg for ACL ipv4 rule number
Date: 10 Oct 2020 23:03:05 -0700 [thread overview]
Message-ID: <def01d$8t2p9j@fmsmga008-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/79128
_apply issues_
Submitter: Simei Su <simei.su@intel.com>
Date: 2020-09-29 01:56:32
Reply_mail: 20200929015632.109364-5-simei.su@intel.com
DPDK git baseline:
Repo:dpdk-next-net-intel, CommitID: 900d834cf64bc8be63d821a3e6493ba78084e67b
Repo:dpdk, CommitID: 8e6fa199d1e7ec032a4cbb5e80276cbfad02098e
* Repo: dpdk-next-net-intel
Falling back to patching base and 3-way merge...
Auto-merging drivers/net/ice/ice_dcf_ethdev.c
CONFLICT (content): Merge conflict in drivers/net/ice/ice_dcf_ethdev.c
error: Failed to merge in the changes.
Patch failed at 0004 net/ice: add devarg for ACL ipv4 rule number
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".
* Repo: dpdk
Applying: net/ice: support ACL filter in DCF
error: sha1 information is lacking or useless (doc/guides/rel_notes/release_20_11.rst).
error: could not build fake ancestor
Patch failed at 0003 net/ice: support ACL filter in DCF
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:[~2020-10-11 6:03 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='def01d$8t2p9j@fmsmga008-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).