From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw(86794) [v3, 9/9] net/mlx5: improve bonding xstats
Date: 18 Jan 2021 05:54:24 -0800 [thread overview]
Message-ID: <925d15$bdpsro@orsmga008-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1435 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/86794
_apply issues_
Submitter: Xueming Li <xuemingl@nvidia.com>
Date: 2021-01-18 11:29:13
Reply_mail: 1610969353-31938-10-git-send-email-xuemingl@nvidia.com
DPDK git baseline:
Repo:dpdk-next-net-mlx, CommitID: d70160ce3ac98b2687e7c40bcadee004779b5305
Repo:dpdk, CommitID: e03d2c3c705e40281bda2f11a947f4d3d5e062e6
* Repo: dpdk-next-net-mlx
Applying: net/mlx5: support representor of sub function
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: support representor of sub function
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: support representor of sub function
error: sha1 information is lacking or useless (doc/guides/nics/mlx5.rst).
error: could not build fake ancestor
Patch failed at 0002 net/mlx5: support representor of sub function
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-18 13:54 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='925d15$bdpsro@orsmga008-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).