From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: vasilyf@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw27398 [PATCH 2/2] net/mlx4: get back RX offloads
Date: 03 Aug 2017 03:00:55 -0700 [thread overview]
Message-ID: <e624e2$12gu13b@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 10995 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/27398
_apply patch file failure_
Submitter: Vasily Philipov <vasilyf@mellanox.com>
Date: Thu, 3 Aug 2017 11:49:15 +0300
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:cb78ef9859ff68b9e260a844f151055ebd9ae78f
Repo:dpdk-next-crypto, Branch:master, CommitID:f4709b40940395b29521d6e5e36b58c516a74b29
Repo:dpdk-next-net, Branch:master, CommitID:f4709b40940395b29521d6e5e36b58c516a74b29
Repo:dpdk-next-virtio, Branch:master, CommitID:6c157fe64650167646ff1312f9f7e7dc3674d7eb
Repo:dpdk, Branch:master, CommitID:26857dabb3c91031beb2faab6237969951341a30
Apply patch file failed:
Repo: dpdk
27398:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 succeeded at 6290 with fuzz 2 (offset 5719 lines).
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 107.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej
can't find file to patch at input line 40
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_ethdev.c b/drivers/net/mlx4/mlx4_ethdev.c
|index 8c6b1fd..9b5ba31 100644
|--- a/drivers/net/mlx4/mlx4_ethdev.c
|+++ b/drivers/net/mlx4/mlx4_ethdev.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/mlx4/mlx4_prm.h
can't find file to patch at input line 76
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxq.c b/drivers/net/mlx4/mlx4_rxq.c
|index bbe9c89..c431033 100644
|--- a/drivers/net/mlx4/mlx4_rxq.c
|+++ b/drivers/net/mlx4/mlx4_rxq.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 92
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxtx.c b/drivers/net/mlx4/mlx4_rxtx.c
|index f11c84c..f090354 100644
|--- a/drivers/net/mlx4/mlx4_rxtx.c
|+++ b/drivers/net/mlx4/mlx4_rxtx.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 230
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxtx.h b/drivers/net/mlx4/mlx4_rxtx.h
|index 077fdd8..2f03a94 100644
|--- a/drivers/net/mlx4/mlx4_rxtx.h
|+++ b/drivers/net/mlx4/mlx4_rxtx.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
Repo: dpdk-next-crypto
27398:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 succeeded at 6290 with fuzz 2 (offset 5719 lines).
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 107.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej
can't find file to patch at input line 40
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_ethdev.c b/drivers/net/mlx4/mlx4_ethdev.c
|index 8c6b1fd..9b5ba31 100644
|--- a/drivers/net/mlx4/mlx4_ethdev.c
|+++ b/drivers/net/mlx4/mlx4_ethdev.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/mlx4/mlx4_prm.h
can't find file to patch at input line 76
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxq.c b/drivers/net/mlx4/mlx4_rxq.c
|index bbe9c89..c431033 100644
|--- a/drivers/net/mlx4/mlx4_rxq.c
|+++ b/drivers/net/mlx4/mlx4_rxq.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 92
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxtx.c b/drivers/net/mlx4/mlx4_rxtx.c
|index f11c84c..f090354 100644
|--- a/drivers/net/mlx4/mlx4_rxtx.c
|+++ b/drivers/net/mlx4/mlx4_rxtx.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 230
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxtx.h b/drivers/net/mlx4/mlx4_rxtx.h
|index 077fdd8..2f03a94 100644
|--- a/drivers/net/mlx4/mlx4_rxtx.h
|+++ b/drivers/net/mlx4/mlx4_rxtx.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
Repo: dpdk-next-net
27398:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 succeeded at 6290 with fuzz 2 (offset 5719 lines).
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 107.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej
can't find file to patch at input line 40
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_ethdev.c b/drivers/net/mlx4/mlx4_ethdev.c
|index 8c6b1fd..9b5ba31 100644
|--- a/drivers/net/mlx4/mlx4_ethdev.c
|+++ b/drivers/net/mlx4/mlx4_ethdev.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/mlx4/mlx4_prm.h
can't find file to patch at input line 76
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxq.c b/drivers/net/mlx4/mlx4_rxq.c
|index bbe9c89..c431033 100644
|--- a/drivers/net/mlx4/mlx4_rxq.c
|+++ b/drivers/net/mlx4/mlx4_rxq.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 92
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxtx.c b/drivers/net/mlx4/mlx4_rxtx.c
|index f11c84c..f090354 100644
|--- a/drivers/net/mlx4/mlx4_rxtx.c
|+++ b/drivers/net/mlx4/mlx4_rxtx.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 230
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxtx.h b/drivers/net/mlx4/mlx4_rxtx.h
|index 077fdd8..2f03a94 100644
|--- a/drivers/net/mlx4/mlx4_rxtx.h
|+++ b/drivers/net/mlx4/mlx4_rxtx.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
Repo: dpdk-next-virtio
27398:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 succeeded at 6282 with fuzz 2 (offset 5711 lines).
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 107.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej
can't find file to patch at input line 40
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_ethdev.c b/drivers/net/mlx4/mlx4_ethdev.c
|index 8c6b1fd..9b5ba31 100644
|--- a/drivers/net/mlx4/mlx4_ethdev.c
|+++ b/drivers/net/mlx4/mlx4_ethdev.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/mlx4/mlx4_prm.h
can't find file to patch at input line 76
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxq.c b/drivers/net/mlx4/mlx4_rxq.c
|index bbe9c89..c431033 100644
|--- a/drivers/net/mlx4/mlx4_rxq.c
|+++ b/drivers/net/mlx4/mlx4_rxq.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 92
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxtx.c b/drivers/net/mlx4/mlx4_rxtx.c
|index f11c84c..f090354 100644
|--- a/drivers/net/mlx4/mlx4_rxtx.c
|+++ b/drivers/net/mlx4/mlx4_rxtx.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 230
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxtx.h b/drivers/net/mlx4/mlx4_rxtx.h
|index 077fdd8..2f03a94 100644
|--- a/drivers/net/mlx4/mlx4_rxtx.h
|+++ b/drivers/net/mlx4/mlx4_rxtx.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
Repo: dpdk-next-eventdev
27398:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 succeeded at 6282 with fuzz 2 (offset 5711 lines).
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 107.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej
can't find file to patch at input line 40
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_ethdev.c b/drivers/net/mlx4/mlx4_ethdev.c
|index 8c6b1fd..9b5ba31 100644
|--- a/drivers/net/mlx4/mlx4_ethdev.c
|+++ b/drivers/net/mlx4/mlx4_ethdev.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/mlx4/mlx4_prm.h
can't find file to patch at input line 76
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxq.c b/drivers/net/mlx4/mlx4_rxq.c
|index bbe9c89..c431033 100644
|--- a/drivers/net/mlx4/mlx4_rxq.c
|+++ b/drivers/net/mlx4/mlx4_rxq.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 92
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxtx.c b/drivers/net/mlx4/mlx4_rxtx.c
|index f11c84c..f090354 100644
|--- a/drivers/net/mlx4/mlx4_rxtx.c
|+++ b/drivers/net/mlx4/mlx4_rxtx.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 230
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx4/mlx4_rxtx.h b/drivers/net/mlx4/mlx4_rxtx.h
|index 077fdd8..2f03a94 100644
|--- a/drivers/net/mlx4/mlx4_rxtx.h
|+++ b/drivers/net/mlx4/mlx4_rxtx.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
DPDK STV team
reply other threads:[~2017-08-03 10:00 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='e624e2$12gu13b@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=vasilyf@mellanox.com \
/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).