automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: nelio.laranjeiro@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw18669 [PATCH v5 2/6] net/mlx5: support basic flow items and actions
Date: 29 Dec 2016 08:26:55 -0800	[thread overview]
Message-ID: <587443$mvq8l@orsmga002.jf.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: =?utf-8?q?N=C3=A9lio_Laranjeiro?= <nelio.laranjeiro@6wind.com>
Date: Thu, 29 Dec 2016 16:15:18 +0100
DPDK git baseline: Repo:dpdk-next-crypto, Branch:master, CommitID:8a55340e335968f2a8fc158ce0806633208ef258
                   Repo:dpdk-next-net, Branch:master, CommitID:b7f215bbe3f4642ffff2fa7ec3a61806f1e4d5e3
                   Repo:dpdk-next-virtio, Branch:master, CommitID:584b07eea17fbd5977df4301baae114494855d64
                   Repo:dpdk, Branch:master, CommitID:eac901ce29be559b1bb5c5da33fe2bf5c0b4bfd6
                   
Apply patch file failed:
Repo: dpdk-next-crypto
18669:
patching file drivers/net/mlx5/mlx5.h
Hunk #1 succeeded at 135 (offset -1 lines).
Hunk #2 FAILED at 284.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5.h.rej
can't find file to patch at input line 52
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx5/mlx5_flow.c b/drivers/net/mlx5/mlx5_flow.c
|index 4fdefa0..4f6696e 100644
|--- a/drivers/net/mlx5/mlx5_flow.c
|+++ b/drivers/net/mlx5/mlx5_flow.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
5 out of 5 hunks ignored
patching file drivers/net/mlx5/mlx5_trigger.c

Repo: dpdk-next-net
18669:
patching file drivers/net/mlx5/mlx5.h
Hunk #1 succeeded at 135 (offset -1 lines).
Hunk #2 FAILED at 284.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5.h.rej
can't find file to patch at input line 52
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx5/mlx5_flow.c b/drivers/net/mlx5/mlx5_flow.c
|index 4fdefa0..4f6696e 100644
|--- a/drivers/net/mlx5/mlx5_flow.c
|+++ b/drivers/net/mlx5/mlx5_flow.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
5 out of 5 hunks ignored
patching file drivers/net/mlx5/mlx5_trigger.c

Repo: dpdk-next-virtio
18669:
patching file drivers/net/mlx5/mlx5.h
Hunk #1 succeeded at 135 (offset -1 lines).
Hunk #2 FAILED at 284.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5.h.rej
can't find file to patch at input line 52
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx5/mlx5_flow.c b/drivers/net/mlx5/mlx5_flow.c
|index 4fdefa0..4f6696e 100644
|--- a/drivers/net/mlx5/mlx5_flow.c
|+++ b/drivers/net/mlx5/mlx5_flow.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
5 out of 5 hunks ignored
patching file drivers/net/mlx5/mlx5_trigger.c

Repo: dpdk
18669:
patching file drivers/net/mlx5/mlx5.h
Hunk #1 succeeded at 135 (offset -1 lines).
Hunk #2 FAILED at 284.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5.h.rej
can't find file to patch at input line 52
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx5/mlx5_flow.c b/drivers/net/mlx5/mlx5_flow.c
|index 4fdefa0..4f6696e 100644
|--- a/drivers/net/mlx5/mlx5_flow.c
|+++ b/drivers/net/mlx5/mlx5_flow.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
5 out of 5 hunks ignored
patching file drivers/net/mlx5/mlx5_trigger.c


DPDK STV team

                 reply	other threads:[~2016-12-29 16:26 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='587443$mvq8l@orsmga002.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=nelio.laranjeiro@6wind.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).