From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw68462[v4, 1/5] net/iavf: add support for FDIR basic rule
Date: 15 Apr 2020 12:09:36 -0700 [thread overview]
Message-ID: <fecc85$9t5q2s@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3011 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/68462
_apply issues_
Submitter: Simei Su <simei.su@intel.com>
Date: 2020-04-15 02:55:15
Reply_mail: 1586919319-221220-2-git-send-email-simei.su@intel.com
DPDK git baseline:
Repo:dpdk-next-net-intel, CommitID: 307f086d51d06f73d9337364e1fa1bd34f0425e1
Repo:dpdk, CommitID: d6d084849a1d0c585e0f484809c205652a7b0471
*Repo: dpdk-next-net-intel
SRCS-$(CONFIG_RTE_LIBRTE_IAVF_PMD) += iavf_hash.c
ifeq ($(CONFIG_RTE_ARCH_X86), y)
SRCS-$(CONFIG_RTE_LIBRTE_IAVF_PMD) += iavf_rxtx_vec_sse.c
endif
error: patch failed: drivers/net/iavf/Makefile:25
error: drivers/net/iavf/Makefile: patch does not apply
Checking patch drivers/net/iavf/iavf.h...
Hunk #1 succeeded at 89 (offset -3 lines).
Hunk #2 succeeded at 138 (offset -4 lines).
error: while searching for:
int iavf_add_del_vlan(struct iavf_adapter *adapter, uint16_t vlanid, bool add);
int iavf_add_del_rss_cfg(struct iavf_adapter *adapter,
struct virtchnl_rss_cfg *rss_cfg, bool add);
#endif /* _IAVF_ETHDEV_H_ */
error: patch failed: drivers/net/iavf/iavf.h:254
error: drivers/net/iavf/iavf.h: patch does not apply
Checking patch drivers/net/iavf/iavf_fdir.c...
Checking patch drivers/net/iavf/iavf_vchnl.c...
error: while searching for:
--
VIRTCHNL_VF_OFFLOAD_ADV_RSS_PF;
args.in_args = (uint8_t *)∩︀
args.in_args_size = sizeof(caps);
error: patch failed: drivers/net/iavf/iavf_vchnl.c:337
error: drivers/net/iavf/iavf_vchnl.c: patch does not apply
Checking patch drivers/net/iavf/meson.build...
error: while searching for:
'iavf_vchnl.c',
'iavf_generic_flow.c',
'iavf_hash.c',
)
if arch_subdir == 'x86'
error: patch failed: drivers/net/iavf/meson.build:14
error: drivers/net/iavf/meson.build: patch does not apply
*Repo: dpdk
SRCS-$(CONFIG_RTE_LIBRTE_IAVF_PMD) += iavf_hash.c
ifeq ($(CONFIG_RTE_ARCH_X86), y)
SRCS-$(CONFIG_RTE_LIBRTE_IAVF_PMD) += iavf_rxtx_vec_sse.c
endif
error: patch failed: drivers/net/iavf/Makefile:25
error: drivers/net/iavf/Makefile: patch does not apply
Checking patch drivers/net/iavf/iavf.h...
error: while searching for:
struct iavf_flow_parser_node;
TAILQ_HEAD(iavf_parser_list, iavf_flow_parser_node);
/* TODO: is that correct to assume the max number to be 16 ?*/
#define IAVF_MAX_MSIX_VECTORS 16
error: patch failed: drivers/net/iavf/iavf.h:92
error: drivers/net/iavf/iavf.h: patch does not apply
Checking patch drivers/net/iavf/iavf_fdir.c...
Checking patch drivers/net/iavf/iavf_vchnl.c...
error: while searching for:
--
VIRTCHNL_VF_OFFLOAD_ADV_RSS_PF;
args.in_args = (uint8_t *)∩︀
args.in_args_size = sizeof(caps);
error: patch failed: drivers/net/iavf/iavf_vchnl.c:337
error: drivers/net/iavf/iavf_vchnl.c: patch does not apply
Checking patch drivers/net/iavf/meson.build...
error: while searching for:
'iavf_vchnl.c',
'iavf_generic_flow.c',
'iavf_hash.c',
)
if arch_subdir == 'x86'
error: patch failed: drivers/net/iavf/meson.build:14
error: drivers/net/iavf/meson.build: patch does not apply
DPDK STV team
reply other threads:[~2020-04-15 19: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='fecc85$9t5q2s@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).