From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw63171[v8, 07/12] lpm: remove deprecated code
Date: 21 Nov 2019 06:59:40 -0800 [thread overview]
Message-ID: <ee68f5$8kse1g@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1683 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/63171
_apply issues_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: 2019-11-20 17:23:34
Reply_mail: 0d4028269b34b303e538c02a7b0d62fdbb3b1dec.1574270323.git.anatoly.burakov@intel.com
DPDK git baseline:
Repo:dpdk, CommitID: e5d0ba08703099c12e4bb2eac650cbb047df1a13
*Repo: dpdk
rte_lpm_find_existing_v1604(const char *name)
{
struct rte_lpm *l = NULL;
struct rte_tailq_entry *te;
error: patch failed: lib/librte_lpm/rte_lpm.c:90
error: lib/librte_lpm/rte_lpm.c: patch does not apply
Checking patch lib/librte_lpm/rte_lpm.h...
error: while searching for:
#if RTE_BYTE_ORDER == RTE_LITTLE_ENDIAN
--
__extension__
struct rte_lpm_tbl_entry {
/**
error: patch failed: lib/librte_lpm/rte_lpm.h:64
error: lib/librte_lpm/rte_lpm.h: patch does not apply
Checking patch lib/librte_lpm/rte_lpm6.c...
error: while searching for:
return 1;
}
--
/*
* Simulate adding a route to LPM
*
error: patch failed: lib/librte_lpm/rte_lpm6.c:809
error: lib/librte_lpm/rte_lpm6.c: patch does not apply
Checking patch lib/librte_lpm/rte_lpm6.h...
error: while searching for:
int
rte_lpm6_add(struct rte_lpm6 *lpm, uint8_t *ip, uint8_t depth,
--
uint32_t next_hop);
/**
* Check if a rule is present in the LPM table,
error: patch failed: lib/librte_lpm/rte_lpm6.h:96
error: lib/librte_lpm/rte_lpm6.h: patch does not apply
Checking patch lib/librte_lpm/rte_lpm_version.map...
error: while searching for:
DPDK_2.0 {
global:
--
rte_lpm6_lookup_bulk_func;
local: *;
};
error: patch failed: lib/librte_lpm/rte_lpm_version.map:1
error: lib/librte_lpm/rte_lpm_version.map: patch does not apply
DPDK STV team
reply other threads:[~2019-11-21 14:59 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$8kse1g@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).