From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw71394[02/50] net/bnxt: Infrastructure support for VF-reps data path
Date: 15 Jun 2020 18:28:34 -0700 [thread overview]
Message-ID: <fecc85$af8fq3@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/71394
_apply issues_
Submitter: Somnath Kotur <somnath.kotur@broadcom.com>
Date: 2020-06-12 13:28:46
Reply_mail: 20200612132934.16488-3-somnath.kotur@broadcom.com
DPDK git baseline:
Repo:dpdk, CommitID: 2a5d547a4a9b7b4644e0b75d90d3b577a34e6d11
Repo:dpdk, CommitID: 2a5d547a4a9b7b4644e0b75d90d3b577a34e6d11
* Repo: dpdk-next-net-brcm
/* address space location of register */
error: patch failed: drivers/net/bnxt/bnxt.h:495
error: drivers/net/bnxt/bnxt.h: patch does not apply
Checking patch drivers/net/bnxt/bnxt_ethdev.c...
Hunk #1 succeeded at 156 (offset 19 lines).
--
if (!(BNXT_PF(backing_bp) || BNXT_VF_IS_TRUSTED(backing_bp))) {
error: patch failed: drivers/net/bnxt/bnxt_ethdev.c:5703
error: drivers/net/bnxt/bnxt_ethdev.c: patch does not apply
Checking patch drivers/net/bnxt/bnxt_reps.c...
error: drivers/net/bnxt/bnxt_reps.c: No such file or directory
* Repo: dpdk
/* address space location of register */
error: patch failed: drivers/net/bnxt/bnxt.h:495
error: drivers/net/bnxt/bnxt.h: patch does not apply
Checking patch drivers/net/bnxt/bnxt_ethdev.c...
Hunk #1 succeeded at 156 (offset 19 lines).
--
if (!(BNXT_PF(backing_bp) || BNXT_VF_IS_TRUSTED(backing_bp))) {
error: patch failed: drivers/net/bnxt/bnxt_ethdev.c:5703
error: drivers/net/bnxt/bnxt_ethdev.c: patch does not apply
Checking patch drivers/net/bnxt/bnxt_reps.c...
error: drivers/net/bnxt/bnxt_reps.c: No such file or directory
DPDK STV team
reply other threads:[~2020-06-16 1:28 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='fecc85$af8fq3@orsmga001.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).