From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: nelio.laranjeiro@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw20993 [PATCH v2 6/9] net/mlx5: support flag flow action
Date: 01 Mar 2017 08:33:42 -0800 [thread overview]
Message-ID: <e81775$119btg4@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3004 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/20993
_apply patch file failure_
Submitter: =?utf-8?q?N=C3=A9lio_Laranjeiro?= <nelio.laranjeiro@6wind.com>
Date: Wed, 1 Mar 2017 13:49:45 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:84e6e60a58c840a2fd3c5d6a6f23941b2648cf1c
Repo:dpdk-next-crypto, Branch:master, CommitID:081fefb01748e7063b1b9692af89d8115ec64632
Repo:dpdk-next-net, Branch:master, CommitID:0849925edfaabd2f4ea2ad459638d9ee27a45516
Repo:dpdk-next-virtio, Branch:master, CommitID:850110f0e9c25f6b8a22447e4795a89847c1d00e
Repo:dpdk, Branch:master, CommitID:048ed1d8284b0e91cd940a3edbd8f79861a6b997
Apply patch file failed:
Repo: dpdk
20993:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #2 succeeded at 473 (offset -4 lines).
Hunk #3 succeeded at 1052 (offset -12 lines).
patching file drivers/net/mlx5/mlx5_prm.h
Hunk #1 succeeded at 227 (offset -6 lines).
Hunk #2 succeeded at 243 (offset -6 lines).
patching file drivers/net/mlx5/mlx5_rxtx.c
Hunk #1 FAILED at 1538.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.c.rej
Repo: dpdk-next-crypto
20993:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #2 succeeded at 473 (offset -4 lines).
Hunk #3 succeeded at 1052 (offset -12 lines).
patching file drivers/net/mlx5/mlx5_prm.h
Hunk #1 succeeded at 227 (offset -6 lines).
Hunk #2 succeeded at 243 (offset -6 lines).
patching file drivers/net/mlx5/mlx5_rxtx.c
Hunk #1 FAILED at 1538.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.c.rej
Repo: dpdk-next-net
20993:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #2 succeeded at 473 (offset -4 lines).
Hunk #3 succeeded at 1052 (offset -12 lines).
patching file drivers/net/mlx5/mlx5_prm.h
Hunk #1 succeeded at 227 (offset -6 lines).
Hunk #2 succeeded at 243 (offset -6 lines).
patching file drivers/net/mlx5/mlx5_rxtx.c
Hunk #1 FAILED at 1538.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.c.rej
Repo: dpdk-next-virtio
20993:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #2 succeeded at 473 (offset -4 lines).
Hunk #3 succeeded at 1052 (offset -12 lines).
patching file drivers/net/mlx5/mlx5_prm.h
Hunk #1 succeeded at 227 (offset -6 lines).
Hunk #2 succeeded at 243 (offset -6 lines).
patching file drivers/net/mlx5/mlx5_rxtx.c
Hunk #1 FAILED at 1538.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.c.rej
Repo: dpdk-next-eventdev
20993:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #2 succeeded at 473 (offset -4 lines).
Hunk #3 succeeded at 1052 (offset -12 lines).
patching file drivers/net/mlx5/mlx5_prm.h
Hunk #1 succeeded at 227 (offset -6 lines).
Hunk #2 succeeded at 243 (offset -6 lines).
patching file drivers/net/mlx5/mlx5_rxtx.c
Hunk #1 FAILED at 1538.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.c.rej
DPDK STV team
reply other threads:[~2017-03-01 16:33 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='e81775$119btg4@fmsmga001.fm.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).