From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |WARNING| pw95584 [PATCH] net/bnxt: fix build failure
Date: Thu, 8 Jul 2021 19:14:43 -0400 (EDT) [thread overview]
Message-ID: <20210708231443.ECA887855@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/95584
_apply patch failure_
Submitter: Ajit Khaparde <ajit.khaparde@broadcom.com>
Date: Thursday, July 08 2021 22:49:50
Applied on: CommitID:175af25734f295874e31b33ccd0879e69fd152a9
Apply patch set 95584 failed:
Checking patch drivers/net/bnxt/tf_core/dpool.c...
error: drivers/net/bnxt/tf_core/dpool.c: does not exist in index
Checking patch drivers/net/bnxt/tf_ulp/ulp_mapper.c...
error: while searching for:
struct tf_free_tbl_entry_parms free_parms = { 0 };
uint32_t tbl_scope_id;
struct tf *tfp;
struct bnxt_ulp_glb_resource_info glb_res;
uint16_t bit_size;
bool alloc = false;
bool write = false;
error: patch failed: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2249
Applying patch drivers/net/bnxt/tf_ulp/ulp_mapper.c with 1 reject...
Rejected hunk #1.
diff a/drivers/net/bnxt/tf_ulp/ulp_mapper.c b/drivers/net/bnxt/tf_ulp/ulp_mapper.c (rejected hunks)
@@ -2249,7 +2249,7 @@ ulp_mapper_index_tbl_process(struct bnxt_ulp_mapper_parms *parms,
struct tf_free_tbl_entry_parms free_parms = { 0 };
uint32_t tbl_scope_id;
struct tf *tfp;
- struct bnxt_ulp_glb_resource_info glb_res;
+ struct bnxt_ulp_glb_resource_info glb_res = { 0 };
uint16_t bit_size;
bool alloc = false;
bool write = false;
https://lab.dpdk.org/results/dashboard/patchsets/17738/
UNH-IOL DPDK Community Lab
reply other threads:[~2021-07-08 23:14 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=20210708231443.ECA887855@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).