automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report]  |FAILURE| pw41687[v2, 13/20] net/mlx5: add RSS flow action
Date: 27 Jun 2018 08:16:28 -0700	[thread overview]
Message-ID: <0590c7$21131g@orsmga001.jf.intel.com> (raw)

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

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

_apply issues_

Submitter: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
Date: 2018-06-27 15:07:45
DPDK git baseline:
	Repo:dpdk-master, CommitID: d67014c3d38b20ac4cfe103f5a7a2107feaa5acf
	Repo:dpdk-next-eventdev, CommitID: 5ddd8c979d9ff94e5c266fca20cb179b1826bcab
	Repo:dpdk-next-net, CommitID: 6d722aec4453d0180b0109c620ec2d8037a5bb11
	Repo:dpdk-next-crypto, CommitID: 3ea5377b64c0daedb666a640900fc93af682ba34
	Repo:dpdk-next-virtio, CommitID: bc34445d488087b0dcc1313d0391eb8b009ec7a6

*Repo: dpdk-master
Checking patch drivers/net/mlx5/mlx5_flow.c...
error: while searching for:
/* Action fate on the packet. */
#define MLX5_FLOW_FATE_DROP (1u << 0)
#define MLX5_FLOW_FATE_QUEUE (1u << 1)

/* Modify a packet. */
--
struct mlx5_flow_verbs {
	unsigned int size; /**< Size of the attribute. */
	struct {
		struct ibv_flow_attr *attr;

error: patch failed: drivers/net/mlx5/mlx5_flow.c:51
error: drivers/net/mlx5/mlx5_flow.c: patch does not apply
*Repo: dpdk-next-eventdev
Checking patch drivers/net/mlx5/mlx5_flow.c...
error: while searching for:
/* Action fate on the packet. */
#define MLX5_FLOW_FATE_DROP (1u << 0)
#define MLX5_FLOW_FATE_QUEUE (1u << 1)

/* Modify a packet. */
--
struct mlx5_flow_verbs {
	unsigned int size; /**< Size of the attribute. */
	struct {
		struct ibv_flow_attr *attr;

error: patch failed: drivers/net/mlx5/mlx5_flow.c:51
error: drivers/net/mlx5/mlx5_flow.c: patch does not apply
*Repo: dpdk-next-net
Checking patch drivers/net/mlx5/mlx5_flow.c...
error: while searching for:
/* Action fate on the packet. */
#define MLX5_FLOW_FATE_DROP (1u << 0)
#define MLX5_FLOW_FATE_QUEUE (1u << 1)

/* Modify a packet. */
--
struct mlx5_flow_verbs {
	unsigned int size; /**< Size of the attribute. */
	struct {
		struct ibv_flow_attr *attr;

error: patch failed: drivers/net/mlx5/mlx5_flow.c:51
error: drivers/net/mlx5/mlx5_flow.c: patch does not apply
*Repo: dpdk-next-crypto
Checking patch drivers/net/mlx5/mlx5_flow.c...
error: while searching for:
/* Action fate on the packet. */
#define MLX5_FLOW_FATE_DROP (1u << 0)
#define MLX5_FLOW_FATE_QUEUE (1u << 1)

/* Modify a packet. */
--
struct mlx5_flow_verbs {
	unsigned int size; /**< Size of the attribute. */
	struct {
		struct ibv_flow_attr *attr;

error: patch failed: drivers/net/mlx5/mlx5_flow.c:51
error: drivers/net/mlx5/mlx5_flow.c: patch does not apply
*Repo: dpdk-next-virtio
Checking patch drivers/net/mlx5/mlx5_flow.c...
error: while searching for:
/* Action fate on the packet. */
#define MLX5_FLOW_FATE_DROP (1u << 0)
#define MLX5_FLOW_FATE_QUEUE (1u << 1)

/* Modify a packet. */
--
struct mlx5_flow_verbs {
	unsigned int size; /**< Size of the attribute. */
	struct {
		struct ibv_flow_attr *attr;

error: patch failed: drivers/net/mlx5/mlx5_flow.c:51
error: drivers/net/mlx5/mlx5_flow.c: patch does not apply

DPDK STV team

                 reply	other threads:[~2018-06-27 15:16 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$21131g@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).