From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: matan@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw28509 [PATCH v5] net/mlx5: support device removal event
Date: 08 Sep 2017 04:17:25 -0700 [thread overview]
Message-ID: <a2ed28$147uj0n@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3307 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/28509
_apply patch file failure_
Submitter: Matan Azrad <matan@mellanox.com>
Date: Fri, 8 Sep 2017 13:47:45 +0300
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:85238f501ec36bc6f0e15e6434296312841259bd
Repo:dpdk-next-crypto, Branch:master, CommitID:12f47db9b73e9ea82702b4ab128df20fc9bc0f5f
Repo:dpdk-next-net, Branch:master, CommitID:5362cc7ff322e05ece437375ed19be6db990304d
Repo:dpdk-next-virtio, Branch:master, CommitID:6c157fe64650167646ff1312f9f7e7dc3674d7eb
Repo:dpdk, Branch:master, CommitID:06791a4bcedf3eb97f05c13debff90272e3b0d54
Apply patch file failed:
Repo: dpdk
28509:
patching file doc/guides/nics/features/mlx5.ini
patching file drivers/net/mlx5/mlx5.c
Hunk #1 succeeded at 901 (offset 31 lines).
patching file drivers/net/mlx5/mlx5_ethdev.c
Hunk #1 FAILED at 1172.
Hunk #2 succeeded at 1212 with fuzz 1 (offset -15 lines).
Hunk #3 succeeded at 1228 (offset -15 lines).
Hunk #4 succeeded at 1254 (offset -15 lines).
Hunk #5 succeeded at 1263 (offset -15 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_ethdev.c.rej
Repo: dpdk-next-crypto
28509:
patching file doc/guides/nics/features/mlx5.ini
patching file drivers/net/mlx5/mlx5.c
Hunk #1 succeeded at 901 (offset 31 lines).
patching file drivers/net/mlx5/mlx5_ethdev.c
Hunk #1 FAILED at 1172.
Hunk #2 succeeded at 1212 with fuzz 1 (offset -15 lines).
Hunk #3 succeeded at 1228 (offset -15 lines).
Hunk #4 succeeded at 1254 (offset -15 lines).
Hunk #5 succeeded at 1263 (offset -15 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_ethdev.c.rej
Repo: dpdk-next-net
28509:
patching file doc/guides/nics/features/mlx5.ini
patching file drivers/net/mlx5/mlx5.c
Hunk #1 succeeded at 871 (offset 1 line).
patching file drivers/net/mlx5/mlx5_ethdev.c
Hunk #1 FAILED at 1172.
Hunk #2 succeeded at 1201 with fuzz 1 (offset -26 lines).
Hunk #3 succeeded at 1217 (offset -26 lines).
Hunk #4 succeeded at 1243 (offset -26 lines).
Hunk #5 succeeded at 1252 (offset -26 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_ethdev.c.rej
Repo: dpdk-next-virtio
28509:
patching file doc/guides/nics/features/mlx5.ini
patching file drivers/net/mlx5/mlx5.c
Hunk #1 succeeded at 877 (offset 7 lines).
patching file drivers/net/mlx5/mlx5_ethdev.c
Hunk #1 FAILED at 1172.
Hunk #2 succeeded at 1264 with fuzz 1 (offset 37 lines).
Hunk #3 succeeded at 1303 (offset 60 lines).
Hunk #4 succeeded at 1329 (offset 60 lines).
Hunk #5 succeeded at 1338 (offset 60 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_ethdev.c.rej
Repo: dpdk-next-eventdev
28509:
patching file doc/guides/nics/features/mlx5.ini
patching file drivers/net/mlx5/mlx5.c
Hunk #1 succeeded at 901 (offset 31 lines).
patching file drivers/net/mlx5/mlx5_ethdev.c
Hunk #1 FAILED at 1172.
Hunk #2 succeeded at 1212 with fuzz 1 (offset -15 lines).
Hunk #3 succeeded at 1228 (offset -15 lines).
Hunk #4 succeeded at 1254 (offset -15 lines).
Hunk #5 succeeded at 1263 (offset -15 lines).
1 out of 5 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_ethdev.c.rej
DPDK STV team
reply other threads:[~2017-09-08 11:17 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='a2ed28$147uj0n@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=matan@mellanox.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).