From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: adrien.mazarguil@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw30139 [PATCH v1 18/29] net/mlx4: add VLAN filter configuration support
Date: 12 Oct 2017 22:25:41 -0700 [thread overview]
Message-ID: <8a7c36$136omm8@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3048 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/30139
_apply patch file failure_
Submitter: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Date: Wed, 11 Oct 2017 16:35:30 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:457f7a1876b56fa254eec1c36f429d62b92734bd
Repo:dpdk-next-crypto, Branch:master, CommitID:84e0ded38ac5564f89576843466e2385128c83f2
Repo:dpdk-next-net, Branch:master, CommitID:8c49d5f1c219d986bb129c61dfa2e155d7f2b1da
Repo:dpdk-next-virtio, Branch:master, CommitID:7fbf963714bf7525a28024c5f54bba2b4b3b1a1f
Repo:dpdk, Branch:master, CommitID:c7e4a134e769336bc206a33024bab4dd503563d0
Apply patch file failed:
Repo: dpdk-next-net
30139:
patching file doc/guides/nics/features/mlx4.ini
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/nics/features/mlx4.ini.rej
patching file drivers/net/mlx4/mlx4.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/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
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/mlx4/mlx4.h.rej
patching file drivers/net/mlx4/mlx4_ethdev.c
Hunk #1 succeeded at 721 (offset 133 lines).
patching file drivers/net/mlx4/mlx4_flow.c
Hunk #1 FAILED at 1009.
Hunk #2 succeeded at 1239 with fuzz 2 (offset 205 lines).
Hunk #3 succeeded at 1257 with fuzz 1 (offset 209 lines).
Hunk #4 FAILED at 1067.
Hunk #5 FAILED at 1095.
Hunk #6 FAILED at 1117.
4 out of 6 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4_flow.c.rej
Repo: dpdk-next-virtio
30139:
patching file doc/guides/nics/features/mlx4.ini
patching file drivers/net/mlx4/mlx4.c
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 128.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej
patching file drivers/net/mlx4/mlx4_ethdev.c
patching file drivers/net/mlx4/mlx4_flow.c
Hunk #1 succeeded at 1012 (offset 3 lines).
Hunk #2 succeeded at 1061 (offset 2 lines).
Hunk #3 succeeded at 1075 (offset 2 lines).
Hunk #4 succeeded at 1094 (offset 2 lines).
Hunk #5 succeeded at 1145 (offset 2 lines).
Hunk #6 succeeded at 1173 (offset 2 lines).
Repo: dpdk-next-eventdev
30139:
patching file doc/guides/nics/features/mlx4.ini
patching file drivers/net/mlx4/mlx4.c
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 128.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej
patching file drivers/net/mlx4/mlx4_ethdev.c
patching file drivers/net/mlx4/mlx4_flow.c
Hunk #1 succeeded at 1012 (offset 3 lines).
Hunk #2 succeeded at 1061 (offset 2 lines).
Hunk #3 succeeded at 1075 (offset 2 lines).
Hunk #4 succeeded at 1094 (offset 2 lines).
Hunk #5 succeeded at 1145 (offset 2 lines).
Hunk #6 succeeded at 1173 (offset 2 lines).
DPDK STV team
reply other threads:[~2017-10-13 5:25 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$136omm8@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=adrien.mazarguil@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).