From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw(86042) [v3, 19/19] common/mlx5: remove doorbell allocation API
Date: 06 Jan 2021 04:10:49 -0800 [thread overview]
Message-ID: <f92755$aei9eb@fmsmga008-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1697 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/86042
_apply issues_
Submitter: Michael Baum <michaelba@nvidia.com>
Date: 2021-01-06 08:19:41
Reply_mail: 1609921181-5019-20-git-send-email-michaelba@nvidia.com
DPDK git baseline:
Repo:dpdk-next-net, CommitID: e900da0f4fa51fabd020d79b96b1bc731c6e1eed
Repo:dpdk, CommitID: b031e13d7f0dc7cba9bc5befe968b67832021a59
* Repo: dpdk-next-net
Applying: net/mlx5: remove CQE padding device argument
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: remove CQE padding device argument
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
build: fix plugin load on static build
When dpdk is compiled as static libraries, it is not possible
to load a plugin from an application. We get the following error:
EAL: librte_pmd_xxxx.so: undefined symbol: per_lcore__rte_errno
--
Applying: net/mlx5: remove CQE padding device argument
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: remove CQE padding device argument
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-06 12:10 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='f92755$aei9eb@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).