From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: erezf@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw34584 [PATCH] net/mlx5: fix MTU update Changing the MTU is not related to changing the number of segments activating or not the multi-segment support should be handled by the application.
Date: 28 Jan 2018 06:08:14 -0800 [thread overview]
Message-ID: <a797f1$os3sv@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1674 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/34584
_apply patch file failure_
Submitter: Erez Ferber <erezf@mellanox.com>
Date: Sun, 28 Jan 2018 15:39:47 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:bf375b4d51170cd58ca50c646781cb6de17766ea
Repo:dpdk-next-crypto, Branch:master, CommitID:b50ff008a5e23864c06a44981b848db60fced6ec
Repo:dpdk-next-net, Branch:master, CommitID:76e25c76f322db9be9d6c8b95a5bfb6d78ddf988
Repo:dpdk-next-virtio, Branch:master, CommitID:a1a1310df30fddaf25a6e23cff18c36969075131
Repo:dpdk, Branch:master, CommitID:1742c2d9fab07e66209f2d14e7daa50829fc4423
Apply patch file failed:
Repo: dpdk
34584:
patching file drivers/net/mlx5/mlx5_ethdev.c
Hunk #1 FAILED at 930.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5_ethdev.c.rej
Repo: dpdk-next-crypto
34584:
patching file drivers/net/mlx5/mlx5_ethdev.c
Hunk #1 FAILED at 930.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5_ethdev.c.rej
Repo: dpdk-next-net
34584:
patching file drivers/net/mlx5/mlx5_ethdev.c
Hunk #1 FAILED at 930.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5_ethdev.c.rej
Repo: dpdk-next-virtio
34584:
patching file drivers/net/mlx5/mlx5_ethdev.c
Hunk #1 FAILED at 930.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5_ethdev.c.rej
Repo: dpdk-next-eventdev
34584:
patching file drivers/net/mlx5/mlx5_ethdev.c
Hunk #1 FAILED at 930.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5_ethdev.c.rej
DPDK STV team
reply other threads:[~2018-01-28 14:08 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='a797f1$os3sv@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=erezf@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).