From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw62816[v2] ethdev: reserve space in main structs for extension
Date: 13 Nov 2019 02:28:54 -0800 [thread overview]
Message-ID: <ee68f5$8ig327@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1629 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/62816
_apply issues_
Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: 2019-11-11 07:26:09
Reply_mail: 20191111072609.6649-1-thomas@monjalon.net
DPDK git baseline:
Repo:dpdk-next-net, CommitID: 79af6d1336abd6012db15485e7a0a79fa5fd0a15
Repo:dpdk, CommitID: 08a234788ee548796fd6b394c7e897a2bf1df1b3
*Repo: dpdk-next-net
uint64_t offloads;
};
/**
error: patch failed: lib/librte_ethdev/rte_ethdev.h:402
error: lib/librte_ethdev/rte_ethdev.h: patch does not apply
Checking patch lib/librte_ethdev/rte_ethdev_core.h...
error: while searching for:
struct rte_eth_rxtx_callback *pre_tx_burst_cbs[RTE_MAX_QUEUES_PER_PORT];
enum rte_eth_dev_state state; /**< Flag indicating the port state */
void *security_ctx; /**< Context for security ops */
} __rte_cache_aligned;
struct rte_eth_dev_sriov;
error: patch failed: lib/librte_ethdev/rte_ethdev_core.h:785
error: lib/librte_ethdev/rte_ethdev_core.h: patch does not apply
*Repo: dpdk
uint64_t offloads;
};
/**
error: patch failed: lib/librte_ethdev/rte_ethdev.h:402
error: lib/librte_ethdev/rte_ethdev.h: patch does not apply
Checking patch lib/librte_ethdev/rte_ethdev_core.h...
error: while searching for:
struct rte_eth_rxtx_callback *pre_tx_burst_cbs[RTE_MAX_QUEUES_PER_PORT];
enum rte_eth_dev_state state; /**< Flag indicating the port state */
void *security_ctx; /**< Context for security ops */
} __rte_cache_aligned;
struct rte_eth_dev_sriov;
error: patch failed: lib/librte_ethdev/rte_ethdev_core.h:785
error: lib/librte_ethdev/rte_ethdev_core.h: patch does not apply
DPDK STV team
reply other threads:[~2019-11-13 10:28 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$8ig327@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).