From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw66719[2/4] event/octeontx: add framework for Rx/Tx offloads
Date: 17 Mar 2020 21:02:07 -0700 [thread overview]
Message-ID: <fecc85$9l16s3@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/66719
_apply issues_
Submitter: Harman Kalra <hkalra@marvell.com>
Date: 2020-03-16 15:29:11
Reply_mail: 1584372553-28710-3-git-send-email-hkalra@marvell.com
DPDK git baseline:
Repo:dpdk, CommitID: 716f9bb42ecb6df640d4dffebe1ec55aaab29ba0
*Repo: dpdk
static void
ssovf_info_get(struct rte_eventdev *dev, struct rte_event_dev_info *dev_info)
{
error: patch failed: drivers/event/octeontx/ssovf_evdev.c:137
error: drivers/event/octeontx/ssovf_evdev.c: patch does not apply
Checking patch drivers/event/octeontx/ssovf_evdev.h...
error: while searching for:
#include "octeontx_rxtx.h"
#define EVENTDEV_NAME_OCTEONTX_PMD event_octeontx
#define SSOVF_LOG(level, fmt, args...) \
error: patch failed: drivers/event/octeontx/ssovf_evdev.h:14
error: drivers/event/octeontx/ssovf_evdev.h: patch does not apply
Checking patch drivers/event/octeontx/ssovf_worker.c...
error: while searching for:
ssows_swtag_untag(ws);
}
--
}
__rte_always_inline uint16_t __hot
ssows_enq(void *port, const struct rte_event *ev)
error: patch failed: drivers/event/octeontx/ssovf_worker.c:91
error: drivers/event/octeontx/ssovf_worker.c: patch does not apply
Checking patch drivers/net/octeontx/octeontx_rxtx.h...
error: while searching for:
NOFF_F | OL3OL4CSUM_F | L3L4CSUM_F | \
MULT_F)
#endif /* __OCTEONTX_RXTX_H__ */
error: patch failed: drivers/net/octeontx/octeontx_rxtx.h:488
error: drivers/net/octeontx/octeontx_rxtx.h: patch does not apply
DPDK STV team
reply other threads:[~2020-03-18 4:02 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$9l16s3@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).