From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: adrien.mazarguil@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw27356 [PATCH v1 42/48] net/mlx4: separate device control functions
Date: 01 Aug 2017 10:57:04 -0700 [thread overview]
Message-ID: <e81775$133vcnf@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5087 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/27356
_apply patch file failure_
Submitter: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Date: Tue, 1 Aug 2017 18:53:59 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:cb78ef9859ff68b9e260a844f151055ebd9ae78f
Repo:dpdk-next-crypto, Branch:master, CommitID:f4709b40940395b29521d6e5e36b58c516a74b29
Repo:dpdk-next-net, Branch:master, CommitID:f4709b40940395b29521d6e5e36b58c516a74b29
Repo:dpdk-next-virtio, Branch:master, CommitID:6c157fe64650167646ff1312f9f7e7dc3674d7eb
Repo:dpdk, Branch:master, CommitID:f4709b40940395b29521d6e5e36b58c516a74b29
Apply patch file failed:
Repo: dpdk
27356:
patching file drivers/net/mlx4/Makefile
Hunk #1 succeeded at 36 with fuzz 2.
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 41.
Hunk #2 FAILED at 86.
Hunk #3 FAILED at 1726.
Hunk #4 succeeded at 4802 (offset 2687 lines).
Hunk #5 FAILED at 2126.
Hunk #6 FAILED at 2187.
Hunk #7 succeeded at 5672 with fuzz 2 (offset 3216 lines).
Hunk #8 succeeded at 5691 (offset 3217 lines).
Hunk #9 succeeded at 5699 with fuzz 2 (offset 3217 lines).
Hunk #10 succeeded at 5767 with fuzz 1 (offset 3242 lines).
5 out of 10 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 34.
Hunk #2 FAILED at 117.
2 out of 2 hunks 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_utils.h
Repo: dpdk-next-crypto
27356:
patching file drivers/net/mlx4/Makefile
Hunk #1 succeeded at 36 with fuzz 2.
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 41.
Hunk #2 FAILED at 86.
Hunk #3 FAILED at 1726.
Hunk #4 succeeded at 4802 (offset 2687 lines).
Hunk #5 FAILED at 2126.
Hunk #6 FAILED at 2187.
Hunk #7 succeeded at 5672 with fuzz 2 (offset 3216 lines).
Hunk #8 succeeded at 5691 (offset 3217 lines).
Hunk #9 succeeded at 5699 with fuzz 2 (offset 3217 lines).
Hunk #10 succeeded at 5767 with fuzz 1 (offset 3242 lines).
5 out of 10 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 34.
Hunk #2 FAILED at 117.
2 out of 2 hunks 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_utils.h
Repo: dpdk-next-net
27356:
patching file drivers/net/mlx4/Makefile
Hunk #1 succeeded at 36 with fuzz 2.
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 41.
Hunk #2 FAILED at 86.
Hunk #3 FAILED at 1726.
Hunk #4 succeeded at 4802 (offset 2687 lines).
Hunk #5 FAILED at 2126.
Hunk #6 FAILED at 2187.
Hunk #7 succeeded at 5672 with fuzz 2 (offset 3216 lines).
Hunk #8 succeeded at 5691 (offset 3217 lines).
Hunk #9 succeeded at 5699 with fuzz 2 (offset 3217 lines).
Hunk #10 succeeded at 5767 with fuzz 1 (offset 3242 lines).
5 out of 10 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 34.
Hunk #2 FAILED at 117.
2 out of 2 hunks 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_utils.h
Repo: dpdk-next-virtio
27356:
patching file drivers/net/mlx4/Makefile
Hunk #1 succeeded at 36 with fuzz 2.
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 41.
Hunk #2 FAILED at 86.
Hunk #3 FAILED at 1726.
Hunk #4 succeeded at 4802 (offset 2687 lines).
Hunk #5 FAILED at 2126.
Hunk #6 FAILED at 2187.
Hunk #7 succeeded at 5666 with fuzz 2 (offset 3210 lines).
Hunk #8 succeeded at 5684 (offset 3210 lines).
Hunk #9 succeeded at 5692 with fuzz 2 (offset 3210 lines).
Hunk #10 succeeded at 5759 with fuzz 1 (offset 3234 lines).
5 out of 10 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 34.
Hunk #2 FAILED at 117.
2 out of 2 hunks 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_utils.h
Repo: dpdk-next-eventdev
27356:
patching file drivers/net/mlx4/Makefile
Hunk #1 succeeded at 36 with fuzz 2.
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 41.
Hunk #2 FAILED at 86.
Hunk #3 FAILED at 1726.
Hunk #4 succeeded at 4802 (offset 2687 lines).
Hunk #5 FAILED at 2126.
Hunk #6 FAILED at 2187.
Hunk #7 succeeded at 5666 with fuzz 2 (offset 3210 lines).
Hunk #8 succeeded at 5684 (offset 3210 lines).
Hunk #9 succeeded at 5692 with fuzz 2 (offset 3210 lines).
Hunk #10 succeeded at 5759 with fuzz 1 (offset 3234 lines).
5 out of 10 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 34.
Hunk #2 FAILED at 117.
2 out of 2 hunks 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_utils.h
DPDK STV team
reply other threads:[~2017-08-01 17:57 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$133vcnf@fmsmga001.fm.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).