From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw(86494) [v2] net/bnxt: code refactoring changes
Date: 13 Jan 2021 18:26:31 -0800 [thread overview]
Message-ID: <93cfb9$h1mb6o@fmsmga005-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/86494
_apply issues_
Submitter: Ajit Khaparde <ajitkhaparde@gmail.com>
Date: 2021-01-14 02:19:14
Reply_mail: 20210114021914.6282-1-ajit.khaparde@broadcom.com
DPDK git baseline:
Repo:dpdk-next-net-brcm, CommitID: ff78ab4ec593a1696d0431b6eebd469420a50de0
Repo:dpdk, CommitID: 6e4d4a6381c47cfe6d75225945b3f6a5f8453214
* Repo: dpdk-next-net-brcm
Applying: net/bnxt: code refactoring changes
error: sha1 information is lacking or useless (drivers/net/bnxt/bnxt_ethdev.c).
error: could not build fake ancestor
Patch failed at 0001 net/bnxt: code refactoring changes
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/bnxt: code refactoring changes
error: sha1 information is lacking or useless (drivers/net/bnxt/bnxt_ethdev.c).
error: could not build fake ancestor
Patch failed at 0001 net/bnxt: code refactoring changes
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-14 2:26 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$h1mb6o@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).