From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: adrien.mazarguil@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw28247 [PATCH v2 48/51] net/mlx4: separate memory management functions
Date: 04 Sep 2017 07:06:32 -0700 [thread overview]
Message-ID: <7327ef$3teejc@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3272 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/28247
_apply patch file failure_
Submitter: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Date: Fri, 1 Sep 2017 10:06:50 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:85238f501ec36bc6f0e15e6434296312841259bd
Repo:dpdk-next-crypto, Branch:master, CommitID:85238f501ec36bc6f0e15e6434296312841259bd
Repo:dpdk-next-net, Branch:master, CommitID:5c489b4543c1ee73bc180f13065c5c5f0633dcb4
Repo:dpdk-next-virtio, Branch:master, CommitID:6c157fe64650167646ff1312f9f7e7dc3674d7eb
Repo:dpdk, Branch:master, CommitID:06791a4bcedf3eb97f05c13debff90272e3b0d54
Apply patch file failed:
Repo: dpdk
28247:
patching file drivers/net/mlx4/Makefile
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/Makefile.rej
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 48.
Hunk #2 FAILED at 110.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 succeeded at 162 (offset 47 lines).
Hunk #2 succeeded at 187 (offset 47 lines).
patching file drivers/net/mlx4/mlx4_mr.c
Repo: dpdk-next-crypto
28247:
patching file drivers/net/mlx4/Makefile
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/Makefile.rej
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 48.
Hunk #2 FAILED at 110.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 succeeded at 162 (offset 47 lines).
Hunk #2 succeeded at 187 (offset 47 lines).
patching file drivers/net/mlx4/mlx4_mr.c
Repo: dpdk-next-net
28247:
patching file drivers/net/mlx4/Makefile
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/Makefile.rej
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 48.
Hunk #2 FAILED at 110.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 succeeded at 162 (offset 47 lines).
Hunk #2 succeeded at 187 (offset 47 lines).
patching file drivers/net/mlx4/mlx4_mr.c
Repo: dpdk-next-virtio
28247:
patching file drivers/net/mlx4/Makefile
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/Makefile.rej
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 48.
Hunk #2 FAILED at 110.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 succeeded at 156 (offset 41 lines).
Hunk #2 succeeded at 181 (offset 41 lines).
patching file drivers/net/mlx4/mlx4_mr.c
Repo: dpdk-next-eventdev
28247:
patching file drivers/net/mlx4/Makefile
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/Makefile.rej
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 48.
Hunk #2 FAILED at 110.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 succeeded at 162 (offset 47 lines).
Hunk #2 succeeded at 187 (offset 47 lines).
patching file drivers/net/mlx4/mlx4_mr.c
DPDK STV team
reply other threads:[~2017-09-04 14:06 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$3teejc@orsmga002.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).