From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw41025[v2] net/ixgbe: fix tunnel type set error for FDIR
Date: 13 Jun 2018 18:50:50 -0700 [thread overview]
Message-ID: <0590c7$1tdgjs@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3631 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/41025
_apply issues_
Submitter: Wei Zhao <wei.zhao1@intel.com>
Date: 2018-06-13 08:11:42
DPDK git baseline:
Repo:dpdk-master, CommitID: 22781f640ed54a2f8f8713116b3d2dca57be9d96
Repo:dpdk-next-eventdev, CommitID: 98c6f0783989170d540537e48d6e65dc656cd731
Repo:dpdk-next-net, CommitID: 238180613562aa6b023e52aef790aa7733cbc8fd
Repo:dpdk-next-crypto, CommitID: 22781f640ed54a2f8f8713116b3d2dca57be9d96
Repo:dpdk-next-virtio, CommitID: bdb72af7a66730d71ff7e2078533f5cd7376326d
*Repo: dpdk-master
Checking patch drivers/net/ixgbe/ixgbe_fdir.c...
error: while searching for:
input->formatted.inner_mac,
fdir_filter->input.flow.tunnel_flow.mac_addr.addr_bytes,
sizeof(input->formatted.inner_mac));
input->formatted.tunnel_type =
fdir_filter->input.flow.tunnel_flow.tunnel_type;
input->formatted.tni_vni =
fdir_filter->input.flow.tunnel_flow.tunnel_id >> 8;
}
error: patch failed: drivers/net/ixgbe/ixgbe_fdir.c:771
error: drivers/net/ixgbe/ixgbe_fdir.c: patch does not apply
Checking patch drivers/net/ixgbe/ixgbe_flow.c...
Hunk #2 succeeded at 2495 (offset 2 lines).
*Repo: dpdk-next-eventdev
Checking patch drivers/net/ixgbe/ixgbe_fdir.c...
error: while searching for:
input->formatted.inner_mac,
fdir_filter->input.flow.tunnel_flow.mac_addr.addr_bytes,
sizeof(input->formatted.inner_mac));
input->formatted.tunnel_type =
fdir_filter->input.flow.tunnel_flow.tunnel_type;
input->formatted.tni_vni =
fdir_filter->input.flow.tunnel_flow.tunnel_id >> 8;
}
error: patch failed: drivers/net/ixgbe/ixgbe_fdir.c:771
error: drivers/net/ixgbe/ixgbe_fdir.c: patch does not apply
Checking patch drivers/net/ixgbe/ixgbe_flow.c...
Hunk #2 succeeded at 2495 (offset 2 lines).
*Repo: dpdk-next-net
Checking patch drivers/net/ixgbe/ixgbe_fdir.c...
error: while searching for:
input->formatted.inner_mac,
fdir_filter->input.flow.tunnel_flow.mac_addr.addr_bytes,
sizeof(input->formatted.inner_mac));
input->formatted.tunnel_type =
fdir_filter->input.flow.tunnel_flow.tunnel_type;
input->formatted.tni_vni =
fdir_filter->input.flow.tunnel_flow.tunnel_id >> 8;
}
error: patch failed: drivers/net/ixgbe/ixgbe_fdir.c:771
error: drivers/net/ixgbe/ixgbe_fdir.c: patch does not apply
Checking patch drivers/net/ixgbe/ixgbe_flow.c...
Hunk #2 succeeded at 2495 (offset 2 lines).
*Repo: dpdk-next-crypto
Checking patch drivers/net/ixgbe/ixgbe_fdir.c...
error: while searching for:
input->formatted.inner_mac,
fdir_filter->input.flow.tunnel_flow.mac_addr.addr_bytes,
sizeof(input->formatted.inner_mac));
input->formatted.tunnel_type =
fdir_filter->input.flow.tunnel_flow.tunnel_type;
input->formatted.tni_vni =
fdir_filter->input.flow.tunnel_flow.tunnel_id >> 8;
}
error: patch failed: drivers/net/ixgbe/ixgbe_fdir.c:771
error: drivers/net/ixgbe/ixgbe_fdir.c: patch does not apply
Checking patch drivers/net/ixgbe/ixgbe_flow.c...
Hunk #2 succeeded at 2495 (offset 2 lines).
*Repo: dpdk-next-virtio
Checking patch drivers/net/ixgbe/ixgbe_fdir.c...
error: while searching for:
input->formatted.inner_mac,
fdir_filter->input.flow.tunnel_flow.mac_addr.addr_bytes,
sizeof(input->formatted.inner_mac));
input->formatted.tunnel_type =
fdir_filter->input.flow.tunnel_flow.tunnel_type;
input->formatted.tni_vni =
fdir_filter->input.flow.tunnel_flow.tunnel_id >> 8;
}
error: patch failed: drivers/net/ixgbe/ixgbe_fdir.c:771
error: drivers/net/ixgbe/ixgbe_fdir.c: patch does not apply
Checking patch drivers/net/ixgbe/ixgbe_flow.c...
Hunk #2 succeeded at 2495 (offset 2 lines).
DPDK STV team
reply other threads:[~2018-06-14 1:50 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='0590c7$1tdgjs@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).