From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw65524[v4, 13/15] drivers/octeontx2: add sec in Tx fastpath framework
Date: 19 Feb 2020 17:08:06 -0800 [thread overview]
Message-ID: <ee68f5$9cudoa@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3125 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/65524
_apply issues_
Submitter: Anoob Joseph <anoobj@marvell.com>
Date: 2020-02-04 11:17:23
Reply_mail: 1580815045-32132-14-git-send-email-anoobj@marvell.com
DPDK git baseline:
Repo:dpdk, CommitID: e6c78e736d776ba15aa040f5d6a29e43a9147c0b
*Repo: dpdk
[f5][f4][f3][f2][f1][f0] = \
otx2_ssogws_dual_tx_adptr_enq_seg_ ## name,
SSO_TX_ADPTR_ENQ_FASTPATH_FUNC
#undef T
error: patch failed: drivers/event/octeontx2/otx2_evdev.c:177
error: drivers/event/octeontx2/otx2_evdev.c: patch does not apply
Checking patch drivers/event/octeontx2/otx2_evdev.h...
error: while searching for:
SSO_RX_ADPTR_ENQ_FASTPATH_FUNC
#undef R
--
#define T(name, f5, f4, f3, f2, f1, f0, sz, flags) \
uint16_t otx2_ssogws_tx_adptr_enq_ ## name(void *port, struct rte_event ev[],\
uint16_t nb_events); \
uint16_t otx2_ssogws_tx_adptr_enq_seg_ ## name(void *port, \
error: patch failed: drivers/event/octeontx2/otx2_evdev.h:335
error: drivers/event/octeontx2/otx2_evdev.h: patch does not apply
Checking patch drivers/event/octeontx2/otx2_worker.c...
error: while searching for:
return 1;
}
--
#define T(name, f5, f4, f3, f2, f1, f0, sz, flags) \
uint16_t __hot \
otx2_ssogws_tx_adptr_enq_ ## name(void *port, struct rte_event ev[], \
uint16_t nb_events) \
error: patch failed: drivers/event/octeontx2/otx2_worker.c:267
error: drivers/event/octeontx2/otx2_worker.c: patch does not apply
Checking patch drivers/event/octeontx2/otx2_worker_dual.c...
error: while searching for:
SSO_RX_ADPTR_ENQ_FASTPATH_FUNC
#undef R
--
#define T(name, f5, f4, f3, f2, f1, f0, sz, flags) \
uint16_t __hot \
otx2_ssogws_dual_tx_adptr_enq_ ## name(void *port, \
struct rte_event ev[], \
error: patch failed: drivers/event/octeontx2/otx2_worker_dual.c:307
error: drivers/event/octeontx2/otx2_worker_dual.c: patch does not apply
Checking patch drivers/net/octeontx2/otx2_ethdev.c...
error: while searching for:
NIX_TX_OFFLOAD_OL3_OL4_CSUM_F |
NIX_TX_OFFLOAD_L3_L4_CSUM_F);
if ((dev->rx_offloads & DEV_RX_OFFLOAD_TIMESTAMP))
flags |= NIX_TX_OFFLOAD_TSTAMP_F;
error: patch failed: drivers/net/octeontx2/otx2_ethdev.c:700
error: drivers/net/octeontx2/otx2_ethdev.c: patch does not apply
Checking patch drivers/net/octeontx2/otx2_tx.c...
error: while searching for:
}
#endif
--
#define T(name, f5, f4, f3, f2, f1, f0, sz, flags) \
static uint16_t __rte_noinline __hot \
otx2_nix_xmit_pkts_ ## name(void *tx_queue, \
struct rte_mbuf **tx_pkts, uint16_t pkts) \
error: patch failed: drivers/net/octeontx2/otx2_tx.c:946
error: drivers/net/octeontx2/otx2_tx.c: patch does not apply
Checking patch drivers/net/octeontx2/otx2_tx.h...
error: while searching for:
#define NIX_TX_OFFLOAD_MBUF_NOFF_F BIT(3)
#define NIX_TX_OFFLOAD_TSTAMP_F BIT(4)
#define NIX_TX_OFFLOAD_TSO_F BIT(5)
/* Flags to control xmit_prepare function.
* Defining it from backwards to denote its been
error: patch failed: drivers/net/octeontx2/otx2_tx.h:12
error: drivers/net/octeontx2/otx2_tx.h: patch does not apply
DPDK STV team
reply other threads:[~2020-02-20 1:08 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='ee68f5$9cudoa@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).