automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report]  |FAILURE| pw65978[Bug, 402] i40e: cannot add rte_flow with ether_type = ARP
Date: 25 Feb 2020 17:04:59 -0800	[thread overview]
Message-ID: <ee68f5$9ei066@orsmga001.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]

Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/65978

_apply issues_

Submitter: bugzilla@dpdk.org
Date: 2020-02-20 17:25:47
Reply_mail: bug-402-3@http.bugs.dpdk.org/
DPDK git baseline:
	Repo:dpdk-next-net-intel, CommitID: b8c5b171527cf7b9d61776c708812cf146b36b94
	Repo:dpdk, CommitID: 93be73ddf0e657262085ce530a6a422896426976

*Repo: dpdk-next-net-intel
ether_type == RTE_ETHER_TYPE_IPV4 ||
                                   ether_type == RTE_ETHER_TYPE_IPV6 ||
                                   ether_type == RTE_ETHER_TYPE_ARP ||
                                   ether_type == outer_tpid) {
                                       rte_flow_error_set(error, EINVAL,
                                                    RTE_FLOW_ERROR_TYPE_I

error: patch failed: drivers/net/i40e/i40e_flow.c:2649
error: drivers/net/i40e/i40e_flow.c: patch does not apply
*Repo: dpdk
ether_type == RTE_ETHER_TYPE_IPV4 ||
                                   ether_type == RTE_ETHER_TYPE_IPV6 ||
                                   ether_type == RTE_ETHER_TYPE_ARP ||
                                   ether_type == outer_tpid) {
                                       rte_flow_error_set(error, EINVAL,
                                                    RTE_FLOW_ERROR_TYPE_I

error: patch failed: drivers/net/i40e/i40e_flow.c:2649
error: drivers/net/i40e/i40e_flow.c: patch does not apply

DPDK STV team

                 reply	other threads:[~2020-02-26  1:05 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$9ei066@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).