From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: nelio.laranjeiro@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw36379 [PATCH v2] net/mlx5: setup RSS regardless of queue count
Date: 21 Mar 2018 09:20:22 -0700 [thread overview]
Message-ID: <ca5293$163q3m@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3089 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/36379
_apply patch file failure_
Submitter: =?utf-8?q?N=C3=A9lio_Laranjeiro?= <nelio.laranjeiro@6wind.com>
Date: Wed, 21 Mar 2018 13:47:51 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:34184d9779e0aa56ab841bb2502b8945e91d8cac
Repo:dpdk-next-crypto, Branch:master, CommitID:7964ded554f3e02a62e8e9a92b9760d0de51346f
Repo:dpdk-next-net, Branch:master, CommitID:576dc0a3843b0d40cd5ce916fafb1dbd19a555e9
Repo:dpdk-next-virtio, Branch:master, CommitID:fc33e147ae5e63a28c2b2c9bec5ad378c612ca36
Repo:dpdk, Branch:master, CommitID:da5957821bdd684a50dcb639fb7798936fb2d981
Apply patch file failed:
Repo: dpdk
36379:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 FAILED at 909.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
patching file drivers/net/mlx5/mlx5_rss.c
Hunk #1 succeeded at 82 with fuzz 2 (offset 40 lines).
Hunk #2 FAILED at 61.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rss.c.rej
patching file drivers/net/mlx5/mlx5_rxq.c
Hunk #1 succeeded at 1028 with fuzz 2 (offset -42 lines).
Repo: dpdk-next-crypto
36379:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 FAILED at 909.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
patching file drivers/net/mlx5/mlx5_rss.c
Hunk #1 succeeded at 82 with fuzz 2 (offset 40 lines).
Hunk #2 FAILED at 61.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rss.c.rej
patching file drivers/net/mlx5/mlx5_rxq.c
Hunk #1 succeeded at 1028 with fuzz 2 (offset -42 lines).
Repo: dpdk-next-net
36379:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 913 with fuzz 2 (offset 4 lines).
patching file drivers/net/mlx5/mlx5_rss.c
Hunk #1 succeeded at 82 with fuzz 2 (offset 40 lines).
Hunk #2 FAILED at 61.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rss.c.rej
patching file drivers/net/mlx5/mlx5_rxq.c
Hunk #1 succeeded at 1028 with fuzz 2 (offset -42 lines).
Repo: dpdk-next-virtio
36379:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 913 with fuzz 2 (offset 4 lines).
patching file drivers/net/mlx5/mlx5_rss.c
Hunk #1 succeeded at 82 with fuzz 2 (offset 40 lines).
Hunk #2 FAILED at 61.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rss.c.rej
patching file drivers/net/mlx5/mlx5_rxq.c
Hunk #1 succeeded at 1028 with fuzz 2 (offset -42 lines).
Repo: dpdk-next-eventdev
36379:
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 FAILED at 909.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
patching file drivers/net/mlx5/mlx5_rss.c
Hunk #1 succeeded at 82 with fuzz 2 (offset 40 lines).
Hunk #2 FAILED at 61.
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rss.c.rej
patching file drivers/net/mlx5/mlx5_rxq.c
Hunk #1 succeeded at 1028 with fuzz 2 (offset -42 lines).
DPDK STV team
reply other threads:[~2018-03-21 16:20 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$163q3m@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=nelio.laranjeiro@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).