[dpdk-test-report] |FAILURE| pw37170[dpdk-dev, v1, 03/16] ethdev: clarify flow API pattern items and actions

[dpdk-test-report] |FAILURE| pw37170[dpdk-dev, v1, 03/16] ethdev: clarify flow API pattern items and actions

[sys_stv]

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

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

_apply issues_

Submitter: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Date: 2018-04-04 15:56:34
DPDK git baseline:
	Repo:dpdk-master, CommitID: 8ea41438832a360aed2b7ba49fb75e310a2ff1dc
	Repo:dpdk-next-eventdev, CommitID: 640b0d1e510e111694c25145466f37867453837f
	Repo:dpdk-next-net, CommitID: 774c1892c434dba09998ccc76b956feb72224571
	Repo:dpdk-next-crypto, CommitID: 728ca9b0d5abea82cd01dee6645456a9d56215f7
	Repo:dpdk-next-virtio, CommitID: 037c0996bc927342f157426739e0cb63f2db8689

*Repo: dpdk-master
Checking patch doc/guides/prog_guide/rte_flow.rst...
error: while searching for:

Pattern items fall in two categories:

- Matching protocol headers and packet data (ANY, RAW, ETH, VLAN, IPV4,
  IPV6, ICMP, UDP, TCP, SCTP, VXLAN, MPLS, GRE, ESP and so on), usually
--
  VF, PORT and so on), often without a specification structure.

Item specification structures are used to match specific values among
protocol fields (or item properties). Documentation describes for each item

error: patch failed: doc/guides/prog_guide/rte_flow.rst:186
error: doc/guides/prog_guide/rte_flow.rst: patch does not apply
Checking patch lib/librte_ether/rte_flow.h...
error: lib/librte_ether/rte_flow.h: No such file or directory
*Repo: dpdk-next-eventdev
Checking patch doc/guides/prog_guide/rte_flow.rst...
error: while searching for:

Pattern items fall in two categories:

- Matching protocol headers and packet data (ANY, RAW, ETH, VLAN, IPV4,
  IPV6, ICMP, UDP, TCP, SCTP, VXLAN, MPLS, GRE, ESP and so on), usually
--
  VF, PORT and so on), often without a specification structure.

Item specification structures are used to match specific values among
protocol fields (or item properties). Documentation describes for each item

error: patch failed: doc/guides/prog_guide/rte_flow.rst:186
error: doc/guides/prog_guide/rte_flow.rst: patch does not apply
Checking patch lib/librte_ether/rte_flow.h...
error: lib/librte_ether/rte_flow.h: No such file or directory
*Repo: dpdk-next-net
Checking patch doc/guides/prog_guide/rte_flow.rst...
error: while searching for:

Pattern items fall in two categories:

- Matching protocol headers and packet data (ANY, RAW, ETH, VLAN, IPV4,
  IPV6, ICMP, UDP, TCP, SCTP, VXLAN, MPLS, GRE, ESP and so on), usually
--
  VF, PORT and so on), often without a specification structure.

Item specification structures are used to match specific values among
protocol fields (or item properties). Documentation describes for each item

error: patch failed: doc/guides/prog_guide/rte_flow.rst:186
error: doc/guides/prog_guide/rte_flow.rst: patch does not apply
Checking patch lib/librte_ether/rte_flow.h...
error: lib/librte_ether/rte_flow.h: No such file or directory
*Repo: dpdk-next-crypto
Checking patch doc/guides/prog_guide/rte_flow.rst...
error: while searching for:

Pattern items fall in two categories:

- Matching protocol headers and packet data (ANY, RAW, ETH, VLAN, IPV4,
  IPV6, ICMP, UDP, TCP, SCTP, VXLAN, MPLS, GRE, ESP and so on), usually
--
  VF, PORT and so on), often without a specification structure.

Item specification structures are used to match specific values among
protocol fields (or item properties). Documentation describes for each item

error: patch failed: doc/guides/prog_guide/rte_flow.rst:186
error: doc/guides/prog_guide/rte_flow.rst: patch does not apply
Checking patch lib/librte_ether/rte_flow.h...
error: lib/librte_ether/rte_flow.h: No such file or directory
*Repo: dpdk-next-virtio
Checking patch doc/guides/prog_guide/rte_flow.rst...
error: while searching for:

Pattern items fall in two categories:

- Matching protocol headers and packet data (ANY, RAW, ETH, VLAN, IPV4,
  IPV6, ICMP, UDP, TCP, SCTP, VXLAN, MPLS, GRE, ESP and so on), usually
--
  VF, PORT and so on), often without a specification structure.

Item specification structures are used to match specific values among
protocol fields (or item properties). Documentation describes for each item

error: patch failed: doc/guides/prog_guide/rte_flow.rst:186
error: doc/guides/prog_guide/rte_flow.rst: patch does not apply
Checking patch lib/librte_ether/rte_flow.h...
error: lib/librte_ether/rte_flow.h: No such file or directory

DPDK STV team