From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw(82321) [v3, 34/34] net/mlx5: remove shared context lock
Date: 27 Oct 2020 06:27:02 -0700 [thread overview]
Message-ID: <569c58$fuv6gb@orsmga005-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/82321
_apply issues_
Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: 2020-10-27 12:27:29
Reply_mail: 1603801650-442376-35-git-send-email-suanmingm@nvidia.com
DPDK git baseline:
Repo:dpdk-next-net-mlx, CommitID: 9c994d9720f27a4860b1c84d2e16b6c7f276ccdd
Repo:dpdk, CommitID: c3afd1cba69bd7a900fd63c02cc87fba8d74430a
* Repo: dpdk-next-net-mlx
Falling back to patching base and 3-way merge...
Auto-merging drivers/net/mlx5/mlx5_flow_verbs.c
CONFLICT (content): Merge conflict in drivers/net/mlx5/mlx5_flow_verbs.c
error: Failed to merge in the changes.
Patch failed at 0002 net/mlx5: use thread specific flow workspace
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/mlx5: use thread specific flow workspace
error: sha1 information is lacking or useless (drivers/net/mlx5/linux/mlx5_os.c).
error: could not build fake ancestor
Patch failed at 0002 net/mlx5: use thread specific flow workspace
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-27 13:27 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='569c58$fuv6gb@orsmga005-auth.jf.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).