From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: vasilyf@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw21415 [PATCH v3 2/2] net/mlx4: support basic flow items and actions
Date: 07 Mar 2017 21:25:16 -0800 [thread overview]
Message-ID: <e81775$11buara@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4660 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/21415
_apply patch file failure_
Submitter: Vasily Philipov <vasilyf@mellanox.com>
Date: Sun, 5 Mar 2017 09:51:32 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:720dbd63fd5083f8cacd6c59aa3f2651121d562a
Repo:dpdk-next-crypto, Branch:master, CommitID:13f57aba3e9f4f6818f525c2e402ac75d5ec7967
Repo:dpdk-next-net, Branch:master, CommitID:bac530ec147c621aaf6988aed6f7f22b75fd0b9d
Repo:dpdk-next-virtio, Branch:master, CommitID:14d3a8536b51f9c1e7d65bcf536b5b348ead1ec1
Repo:dpdk, Branch:master, CommitID:b0c958e14dee3570a684fafb0ef5ca9c86c6f80d
Apply patch file failed:
Repo: dpdk
21415:
patching file drivers/net/mlx4/Makefile
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 72.
Hunk #2 succeeded at 2526 (offset 185 lines).
Hunk #3 succeeded at 4114 (offset 185 lines).
Hunk #4 succeeded at 4134 (offset 185 lines).
Hunk #5 succeeded at 4146 (offset 185 lines).
Hunk #6 succeeded at 4204 (offset 185 lines).
Hunk #7 succeeded at 5206 (offset 185 lines).
Hunk #8 succeeded at 5289 (offset 185 lines).
1 out of 8 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 295.
Hunk #2 FAILED at 337.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej
patching file drivers/net/mlx4/mlx4_flow.c
patching file drivers/net/mlx4/mlx4_flow.h
Repo: dpdk-next-crypto
21415:
patching file drivers/net/mlx4/Makefile
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 72.
Hunk #2 succeeded at 2526 (offset 185 lines).
Hunk #3 succeeded at 4114 (offset 185 lines).
Hunk #4 succeeded at 4134 (offset 185 lines).
Hunk #5 succeeded at 4146 (offset 185 lines).
Hunk #6 succeeded at 4204 (offset 185 lines).
Hunk #7 succeeded at 5206 (offset 185 lines).
Hunk #8 succeeded at 5289 (offset 185 lines).
1 out of 8 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 295.
Hunk #2 FAILED at 337.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej
patching file drivers/net/mlx4/mlx4_flow.c
patching file drivers/net/mlx4/mlx4_flow.h
Repo: dpdk-next-net
21415:
patching file drivers/net/mlx4/Makefile
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 72.
Hunk #2 succeeded at 2526 (offset 185 lines).
Hunk #3 succeeded at 4114 (offset 185 lines).
Hunk #4 succeeded at 4134 (offset 185 lines).
Hunk #5 succeeded at 4146 (offset 185 lines).
Hunk #6 succeeded at 4204 (offset 185 lines).
Hunk #7 succeeded at 5206 (offset 185 lines).
Hunk #8 succeeded at 5289 (offset 185 lines).
1 out of 8 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 295.
Hunk #2 FAILED at 337.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej
patching file drivers/net/mlx4/mlx4_flow.c
patching file drivers/net/mlx4/mlx4_flow.h
Repo: dpdk-next-virtio
21415:
patching file drivers/net/mlx4/Makefile
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 72.
Hunk #2 succeeded at 2526 (offset 185 lines).
Hunk #3 succeeded at 4114 (offset 185 lines).
Hunk #4 succeeded at 4134 (offset 185 lines).
Hunk #5 succeeded at 4146 (offset 185 lines).
Hunk #6 succeeded at 4204 (offset 185 lines).
Hunk #7 succeeded at 5206 (offset 185 lines).
Hunk #8 succeeded at 5289 (offset 185 lines).
1 out of 8 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 295.
Hunk #2 FAILED at 337.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej
patching file drivers/net/mlx4/mlx4_flow.c
patching file drivers/net/mlx4/mlx4_flow.h
Repo: dpdk-next-eventdev
21415:
patching file drivers/net/mlx4/Makefile
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 72.
Hunk #2 succeeded at 2526 (offset 185 lines).
Hunk #3 succeeded at 4114 (offset 185 lines).
Hunk #4 succeeded at 4134 (offset 185 lines).
Hunk #5 succeeded at 4146 (offset 185 lines).
Hunk #6 succeeded at 4204 (offset 185 lines).
Hunk #7 succeeded at 5206 (offset 185 lines).
Hunk #8 succeeded at 5289 (offset 185 lines).
1 out of 8 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 295.
Hunk #2 FAILED at 337.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej
patching file drivers/net/mlx4/mlx4_flow.c
patching file drivers/net/mlx4/mlx4_flow.h
DPDK STV team
next reply other threads:[~2017-03-08 5:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 5:25 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-07 11:59 sys_stv
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$11buara@fmsmga001.fm.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).