From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: rasland@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw29479 [PATCH 3/3] net/mlx5: add Rx HW timestamp
Date: 02 Oct 2017 07:17:51 -0700 [thread overview]
Message-ID: <8a7c36$13374bo@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5933 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/29479
_apply patch file failure_
Submitter: Raslan Darawsheh <rasland@mellanox.com>
Date: Mon, 2 Oct 2017 17:01:04 +0300
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:b4b3260b63d2d8d76ff1c66ab4b70e6d1b6a4bbe
Repo:dpdk-next-crypto, Branch:master, CommitID:51c8fe28d6f6c7329c86a695afc5c7def741fe94
Repo:dpdk-next-net, Branch:master, CommitID:b4fd9dcfcec56db1caa127cd03362500f9d5bd6b
Repo:dpdk-next-virtio, Branch:master, CommitID:fee08fe0d67d46639d25c201738d9b1b867e443c
Repo:dpdk, Branch:master, CommitID:5dce9fcdb2308becb7de7470118af3eeccfe4fd7
Apply patch file failed:
Repo: dpdk
29479:
patching file drivers/net/mlx5/mlx5_ethdev.c
patching file drivers/net/mlx5/mlx5_rxq.c
Hunk #1 FAILED at 609.
Hunk #2 FAILED at 620.
Hunk #3 FAILED at 936.
3 out of 3 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxq.c.rej
patching file drivers/net/mlx5/mlx5_rxtx.c
Hunk #1 succeeded at 1865 with fuzz 2 (offset -22 lines).
patching file drivers/net/mlx5/mlx5_rxtx.h
Hunk #1 succeeded at 107 with fuzz 1 (offset 1 line).
Hunk #2 FAILED at 116.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.h.rej
can't find file to patch at input line 87
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx5/mlx5_rxtx_vec_sse.h b/drivers/net/mlx5/mlx5_rxtx_vec_sse.h
|index c2142d7..e9819b7 100644
|--- a/drivers/net/mlx5/mlx5_rxtx_vec_sse.h
|+++ b/drivers/net/mlx5/mlx5_rxtx_vec_sse.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
Repo: dpdk-next-crypto
29479:
patching file drivers/net/mlx5/mlx5_ethdev.c
patching file drivers/net/mlx5/mlx5_rxq.c
Hunk #1 FAILED at 609.
Hunk #2 FAILED at 620.
Hunk #3 FAILED at 936.
3 out of 3 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxq.c.rej
patching file drivers/net/mlx5/mlx5_rxtx.c
Hunk #1 succeeded at 1865 with fuzz 2 (offset -22 lines).
patching file drivers/net/mlx5/mlx5_rxtx.h
Hunk #1 succeeded at 107 with fuzz 1 (offset 1 line).
Hunk #2 FAILED at 116.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.h.rej
can't find file to patch at input line 87
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx5/mlx5_rxtx_vec_sse.h b/drivers/net/mlx5/mlx5_rxtx_vec_sse.h
|index c2142d7..e9819b7 100644
|--- a/drivers/net/mlx5/mlx5_rxtx_vec_sse.h
|+++ b/drivers/net/mlx5/mlx5_rxtx_vec_sse.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
Repo: dpdk-next-net
29479:
patching file drivers/net/mlx5/mlx5_ethdev.c
Hunk #1 succeeded at 674 (offset -12 lines).
patching file drivers/net/mlx5/mlx5_rxq.c
Hunk #1 FAILED at 609.
Hunk #2 FAILED at 620.
Hunk #3 FAILED at 936.
3 out of 3 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxq.c.rej
patching file drivers/net/mlx5/mlx5_rxtx.c
Hunk #1 succeeded at 1886 (offset -1 lines).
patching file drivers/net/mlx5/mlx5_rxtx.h
Hunk #1 succeeded at 101 with fuzz 1 (offset -5 lines).
Hunk #2 succeeded at 111 (offset -5 lines).
can't find file to patch at input line 87
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx5/mlx5_rxtx_vec_sse.h b/drivers/net/mlx5/mlx5_rxtx_vec_sse.h
|index c2142d7..e9819b7 100644
|--- a/drivers/net/mlx5/mlx5_rxtx_vec_sse.h
|+++ b/drivers/net/mlx5/mlx5_rxtx_vec_sse.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
Repo: dpdk-next-virtio
29479:
patching file drivers/net/mlx5/mlx5_ethdev.c
patching file drivers/net/mlx5/mlx5_rxq.c
Hunk #1 FAILED at 609.
Hunk #2 FAILED at 620.
Hunk #3 FAILED at 936.
3 out of 3 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxq.c.rej
patching file drivers/net/mlx5/mlx5_rxtx.c
Hunk #1 succeeded at 1865 with fuzz 2 (offset -22 lines).
patching file drivers/net/mlx5/mlx5_rxtx.h
Hunk #1 succeeded at 107 with fuzz 1 (offset 1 line).
Hunk #2 FAILED at 116.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.h.rej
can't find file to patch at input line 87
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx5/mlx5_rxtx_vec_sse.h b/drivers/net/mlx5/mlx5_rxtx_vec_sse.h
|index c2142d7..e9819b7 100644
|--- a/drivers/net/mlx5/mlx5_rxtx_vec_sse.h
|+++ b/drivers/net/mlx5/mlx5_rxtx_vec_sse.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
Repo: dpdk-next-eventdev
29479:
patching file drivers/net/mlx5/mlx5_ethdev.c
patching file drivers/net/mlx5/mlx5_rxq.c
Hunk #1 FAILED at 609.
Hunk #2 FAILED at 620.
Hunk #3 FAILED at 936.
3 out of 3 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxq.c.rej
patching file drivers/net/mlx5/mlx5_rxtx.c
Hunk #1 succeeded at 1865 with fuzz 2 (offset -22 lines).
patching file drivers/net/mlx5/mlx5_rxtx.h
Hunk #1 succeeded at 107 with fuzz 1 (offset 1 line).
Hunk #2 FAILED at 116.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.h.rej
can't find file to patch at input line 87
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/mlx5/mlx5_rxtx_vec_sse.h b/drivers/net/mlx5/mlx5_rxtx_vec_sse.h
|index c2142d7..e9819b7 100644
|--- a/drivers/net/mlx5/mlx5_rxtx_vec_sse.h
|+++ b/drivers/net/mlx5/mlx5_rxtx_vec_sse.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
DPDK STV team
reply other threads:[~2017-10-02 14:17 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='8a7c36$13374bo@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=rasland@mellanox.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).