From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |WARNING| pw103236-103237 [PATCH] [2/2] net/iavf: fix build error
Date: Fri, 29 Oct 2021 12:09:02 +0000 (UTC) [thread overview]
Message-ID: <20211029120902.48CB660544@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1672 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/103236
_apply patch failure_
Submitter: Radu Nicolau <radu.nicolau@intel.com>
Date: Friday, October 29 2021 11:14:23
Applied on: CommitID:efb57dd5bbf0ffac645d09ed4d0dbad088b602f1
Apply patch set 103236-103237 failed:
Checking patch drivers/net/iavf/iavf_rxtx.c...
error: while searching for:
((uint64_t)l2tag1 << IAVF_TXD_DATA_QW1_L2TAG1_SHIFT));
}
static inline void
iavf_fill_data_desc_buffer_sz_field(volatile uint64_t *field, uint16_t value)
{
*field |= (((uint64_t)value << IAVF_TXD_DATA_QW1_TX_BUF_SZ_SHIFT) &
IAVF_TXD_DATA_QW1_TX_BUF_SZ_MASK);
}
static inline void
iavf_fill_data_desc(volatile struct iavf_tx_desc *desc,
struct rte_mbuf *m, uint64_t desc_template,
error: patch failed: drivers/net/iavf/iavf_rxtx.c:2396
Applying patch drivers/net/iavf/iavf_rxtx.c with 1 reject...
Rejected hunk #1.
diff a/drivers/net/iavf/iavf_rxtx.c b/drivers/net/iavf/iavf_rxtx.c (rejected hunks)
@@ -2396,13 +2396,6 @@ iavf_build_data_desc_cmd_offset_fields(volatile uint64_t *qw1,
((uint64_t)l2tag1 << IAVF_TXD_DATA_QW1_L2TAG1_SHIFT));
}
-static inline void
-iavf_fill_data_desc_buffer_sz_field(volatile uint64_t *field, uint16_t value)
-{
- *field |= (((uint64_t)value << IAVF_TXD_DATA_QW1_TX_BUF_SZ_SHIFT) &
- IAVF_TXD_DATA_QW1_TX_BUF_SZ_MASK);
- }
-
static inline void
iavf_fill_data_desc(volatile struct iavf_tx_desc *desc,
struct rte_mbuf *m, uint64_t desc_template,
Checking patch drivers/net/iavf/iavf_ipsec_crypto.c...
error: drivers/net/iavf/iavf_ipsec_crypto.c: does not exist in index
https://lab.dpdk.org/results/dashboard/patchsets/19847/
UNH-IOL DPDK Community Lab
reply other threads:[~2021-10-29 12:09 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=20211029120902.48CB660544@dpdk-ubuntu.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).