From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xuemingl@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw40412 [PATCH] net/mlx5: fix memory region cache init
Date: 25 May 2018 00:07:20 -0700 [thread overview]
Message-ID: <ca5293$1nlvle@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3074 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/40412
_apply patch file failure_
Submitter: Xueming Li <xuemingl@mellanox.com>
Date: Fri, 25 May 2018 14:35:38 +0800
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:3c955492b601d65402c02ac81dfdc7eeb62f23c9
Repo:dpdk-next-crypto, Branch:master, CommitID:c9db09ff0eef82cd85a4b5ffe1d7e9efc3907317
Repo:dpdk-next-net, Branch:master, CommitID:a29401fdede12e5fc230ec2b51c06233376a07f3
Repo:dpdk-next-virtio, Branch:master, CommitID:e282c7ebd5c70350346b3e13b32d70a2b4541d5b
Repo:dpdk, Branch:master, CommitID:f16e13c99137687cc880deb7017386f8b80d1a37
Apply patch file failed:
Repo: dpdk
40412:
patching file drivers/net/mlx5/mlx5.c
Hunk #1 FAILED at 1193.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5.c.rej
patching file drivers/net/mlx5/mlx5_ethdev.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/mlx5/mlx5_ethdev.c.rej
patching file drivers/net/mlx5/mlx5_mr.c
Repo: dpdk-next-crypto
40412:
patching file drivers/net/mlx5/mlx5.c
Hunk #1 FAILED at 1193.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5.c.rej
patching file drivers/net/mlx5/mlx5_ethdev.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/mlx5/mlx5_ethdev.c.rej
patching file drivers/net/mlx5/mlx5_mr.c
Repo: dpdk-next-net
40412:
patching file drivers/net/mlx5/mlx5.c
Hunk #1 FAILED at 1193.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5.c.rej
patching file drivers/net/mlx5/mlx5_ethdev.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/mlx5/mlx5_ethdev.c.rej
patching file drivers/net/mlx5/mlx5_mr.c
Repo: dpdk-next-virtio
40412:
patching file drivers/net/mlx5/mlx5.c
Hunk #1 FAILED at 1193.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5.c.rej
patching file drivers/net/mlx5/mlx5_ethdev.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/mlx5/mlx5_ethdev.c.rej
patching file drivers/net/mlx5/mlx5_mr.c
Repo: dpdk-next-eventdev
40412:
patching file drivers/net/mlx5/mlx5.c
Hunk #1 FAILED at 1193.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5.c.rej
patching file drivers/net/mlx5/mlx5_ethdev.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/mlx5/mlx5_ethdev.c.rej
patching file drivers/net/mlx5/mlx5_mr.c
Hunk #1 FAILED at 191.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5_mr.c.rej
DPDK STV team
reply other threads:[~2018-05-25 7:07 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='ca5293$1nlvle@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@mellanox.com \
/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).