automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report]  |FAILURE| pw65296[v2, 08/13] vdpa/mlx5: add basic steering configurations
Date: 17 Feb 2020 06:06:35 -0800	[thread overview]
Message-ID: <ee68f5$9c6hus@orsmga001.jf.intel.com> (raw)

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

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

_apply issues_

Submitter: Matan Azrad <matan@mellanox.com>
Date: 2020-01-29 10:09:04
Reply_mail: 1580292549-27439-9-git-send-email-matan@mellanox.com
DPDK git baseline:
	Repo:dpdk-next-net, CommitID: ef6c28671b5670dd0499a4b2220ec095813e7fe1
	Repo:dpdk, CommitID: 914397d6c1141235b48ca60249221976e9e08feb

*Repo: dpdk-next-net
Author: Manish Chopra <manishc@marvell.com>
Date:   Thu Feb 6 12:01:46 2020 -0800

    net/qede: do not stop vport if not started
    
    Stopping an already disabled vport leads to firmware
    assert. Stop the vport only if it was started.
    
    Fixes: 2ea6f76aff40 ("qede: add core driver")
    Cc: stable@dpdk.org
    
    Signed-off-by: Manish Chopra <manishc@marvell.com>
--
SRCS-$(CONFIG_RTE_LIBRTE_MLX5_VDPA_PMD) += mlx5_vdpa_virtq.c

# Basic CFLAGS.
CFLAGS += -O3

error: patch failed: drivers/vdpa/mlx5/Makefile:11
error: drivers/vdpa/mlx5/Makefile: patch does not apply
Checking patch drivers/vdpa/mlx5/meson.build...
error: while searching for:
	'mlx5_vdpa_mem.c',
	'mlx5_vdpa_event.c',
	'mlx5_vdpa_virtq.c',
)
cflags_options = [
	'-std=c11',

error: patch failed: drivers/vdpa/mlx5/meson.build:15
error: drivers/vdpa/mlx5/meson.build: patch does not apply
Checking patch drivers/vdpa/mlx5/mlx5_vdpa.c...
error: while searching for:
			goto error;
		}
		priv->caps = attr.vdpa;
	}
	priv->ctx = ctx;
	priv->dev_addr.pci_addr = pci_dev->addr;

error: patch failed: drivers/vdpa/mlx5/mlx5_vdpa.c:208
error: drivers/vdpa/mlx5/mlx5_vdpa.c: patch does not apply
Checking patch drivers/vdpa/mlx5/mlx5_vdpa.h...
error: while searching for:
	} umems[3];
};

struct mlx5_vdpa_priv {
	TAILQ_ENTRY(mlx5_vdpa_priv) next;
	int id; /* vDPA device id. */

error: patch failed: drivers/vdpa/mlx5/mlx5_vdpa.h:75
error: drivers/vdpa/mlx5/mlx5_vdpa.h: patch does not apply
Checking patch drivers/vdpa/mlx5/mlx5_vdpa_steer.c...
error: drivers/vdpa/mlx5/mlx5_vdpa_steer.c: already exists in working directory
*Repo: dpdk
SRCS-$(CONFIG_RTE_LIBRTE_MLX5_VDPA_PMD) += mlx5_vdpa_virtq.c

# Basic CFLAGS.
CFLAGS += -O3

error: patch failed: drivers/vdpa/mlx5/Makefile:11
error: drivers/vdpa/mlx5/Makefile: patch does not apply
Checking patch drivers/vdpa/mlx5/meson.build...
error: while searching for:
	'mlx5_vdpa_mem.c',
	'mlx5_vdpa_event.c',
	'mlx5_vdpa_virtq.c',
)
cflags_options = [
	'-std=c11',

error: patch failed: drivers/vdpa/mlx5/meson.build:15
error: drivers/vdpa/mlx5/meson.build: patch does not apply
Checking patch drivers/vdpa/mlx5/mlx5_vdpa.c...
error: while searching for:
			goto error;
		}
		priv->caps = attr.vdpa;
	}
	priv->ctx = ctx;
	priv->dev_addr.pci_addr = pci_dev->addr;

error: patch failed: drivers/vdpa/mlx5/mlx5_vdpa.c:208
error: drivers/vdpa/mlx5/mlx5_vdpa.c: patch does not apply
Checking patch drivers/vdpa/mlx5/mlx5_vdpa.h...
error: while searching for:
	} umems[3];
};

struct mlx5_vdpa_priv {
	TAILQ_ENTRY(mlx5_vdpa_priv) next;
	int id; /* vDPA device id. */

error: patch failed: drivers/vdpa/mlx5/mlx5_vdpa.h:75
error: drivers/vdpa/mlx5/mlx5_vdpa.h: patch does not apply
Checking patch drivers/vdpa/mlx5/mlx5_vdpa_steer.c...
error: drivers/vdpa/mlx5/mlx5_vdpa_steer.c: already exists in working directory

DPDK STV team

                 reply	other threads:[~2020-02-17 14:06 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$9c6hus@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).