automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw71428[36/50] net/bnxt: add index opcode and index operand mapper table
Date: 15 Jun 2020 18:30:06 -0700	[thread overview]
Message-ID: <fecc85$af8g2p@orsmga001.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1517 bytes --]


Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/71428

_apply issues_

Submitter: Somnath Kotur <somnath.kotur@broadcom.com>
Date: 2020-06-12 13:29:20
Reply_mail: 20200612132934.16488-37-somnath.kotur@broadcom.com

DPDK git baseline:
	Repo:dpdk, CommitID: 2a5d547a4a9b7b4644e0b75d90d3b577a34e6d11
	Repo:dpdk, CommitID: 2a5d547a4a9b7b4644e0b75d90d3b577a34e6d11


* Repo: dpdk-next-net-brcm
aparms.dir		= tbl->direction;
	aparms.type		= tbl->resource_type;

error: patch failed: drivers/net/bnxt/tf_ulp/ulp_mapper.c:1517
error: drivers/net/bnxt/tf_ulp/ulp_mapper.c: patch does not apply
Checking patch drivers/net/bnxt/tf_ulp/ulp_template_db_act.c...
error: drivers/net/bnxt/tf_ulp/ulp_template_db_act.c: No such file or directory
--

struct bnxt_ulp_mapper_class_key_field_info {

error: patch failed: drivers/net/bnxt/tf_ulp/ulp_template_struct.h:182
error: drivers/net/bnxt/tf_ulp/ulp_template_struct.h: patch does not apply

* Repo: dpdk
aparms.dir		= tbl->direction;
	aparms.type		= tbl->resource_type;

error: patch failed: drivers/net/bnxt/tf_ulp/ulp_mapper.c:1517
error: drivers/net/bnxt/tf_ulp/ulp_mapper.c: patch does not apply
Checking patch drivers/net/bnxt/tf_ulp/ulp_template_db_act.c...
error: drivers/net/bnxt/tf_ulp/ulp_template_db_act.c: No such file or directory
--

struct bnxt_ulp_mapper_class_key_field_info {

error: patch failed: drivers/net/bnxt/tf_ulp/ulp_template_struct.h:182
error: drivers/net/bnxt/tf_ulp/ulp_template_struct.h: patch does not apply
DPDK STV team

                 reply	other threads:[~2020-06-16  1:30 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$af8g2p@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).