From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: nelio.laranjeiro@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw29958 [PATCH v3 03/30] net/mlx5: prefix Rx structures and functions
Date: 11 Oct 2017 18:55:46 -0700 [thread overview]
Message-ID: <7327ef$4ap5c7@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3313 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/29958
_apply patch file failure_
Submitter: =?utf-8?q?N=C3=A9lio_Laranjeiro?= <nelio.laranjeiro@6wind.com>
Date: Mon, 9 Oct 2017 16:44:48 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:457f7a1876b56fa254eec1c36f429d62b92734bd
Repo:dpdk-next-crypto, Branch:master, CommitID:f255b48dc3e66ca94c5bd60ce20f68ba0eb7f33e
Repo:dpdk-next-net, Branch:master, CommitID:8ec06fbb82d043e115e5740b90c2e7f937bf004a
Repo:dpdk-next-virtio, Branch:master, CommitID:7fbf963714bf7525a28024c5f54bba2b4b3b1a1f
Repo:dpdk, Branch:master, CommitID:63bdef1827f5a98ab375877cb994ef92c33a0b8a
Apply patch file failed:
Repo: dpdk-next-net
29958:
patching file drivers/net/mlx5/mlx5.c
Hunk #1 FAILED at 208.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5.c.rej
patching file drivers/net/mlx5/mlx5.h
Hunk #1 FAILED at 130.
Hunk #2 FAILED at 290.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5.h.rej
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 FAILED at 99.
Hunk #2 FAILED at 1105.
Hunk #3 FAILED at 1301.
Hunk #4 FAILED at 1321.
Hunk #5 FAILED at 1585.
5 out of 5 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
patching file drivers/net/mlx5/mlx5_rxq.c
Hunk #1 FAILED at 374.
Hunk #2 FAILED at 636.
Hunk #3 FAILED at 678.
Hunk #4 FAILED at 720.
Hunk #5 FAILED at 756.
Hunk #6 FAILED at 781.
Hunk #7 FAILED at 848.
Hunk #8 FAILED at 1072.
Hunk #9 FAILED at 1091.
Hunk #10 FAILED at 1122.
Hunk #11 FAILED at 1154.
Hunk #12 FAILED at 1202.
Hunk #13 FAILED at 1212.
Hunk #14 FAILED at 1225.
Hunk #15 FAILED at 1260.
Hunk #16 FAILED at 1328.
Hunk #17 FAILED at 1359.
Hunk #18 FAILED at 1388.
18 out of 18 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxq.c.rej
patching file drivers/net/mlx5/mlx5_rxtx.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
6 out of 6 hunks ignored -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.c.rej
patching file drivers/net/mlx5/mlx5_rxtx.h
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
4 out of 4 hunks ignored -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.h.rej
can't find file to patch at input line 408
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.c b/drivers/net/mlx5/mlx5_rxtx_vec_sse.c
|index 075dce9..b0c87bf 100644
|--- a/drivers/net/mlx5/mlx5_rxtx_vec_sse.c
|+++ b/drivers/net/mlx5/mlx5_rxtx_vec_sse.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
9 out of 9 hunks ignored
patching file drivers/net/mlx5/mlx5_stats.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/net/mlx5/mlx5_stats.c.rej
patching file drivers/net/mlx5/mlx5_vlan.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/net/mlx5/mlx5_vlan.c.rej
DPDK STV team
reply other threads:[~2017-10-12 1:55 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='7327ef$4ap5c7@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).