From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: vasilyf@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw24582 [PATCH v3 2/3] net/mlx4: support for the RSS flow action
Date: 25 May 2017 22:00:21 -0700 [thread overview]
Message-ID: <e81775$12bj4cm@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2730 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/24582
_apply patch file failure_
Submitter: Vasily Philipov <vasilyf@mellanox.com>
Date: Thu, 25 May 2017 17:10:08 +0300
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:776003f4a8e7af4f98338983eb2dfe0a52e8eaf5
Repo:dpdk-next-crypto, Branch:master, CommitID:0766a55d35be8d3d5fe9d1858bb5c3ab648617ce
Repo:dpdk-next-net, Branch:master, CommitID:4265ab2e927c3893f5891f53683ed67466ebd6ad
Repo:dpdk-next-virtio, Branch:master, CommitID:e6e331efc565b36490fee1235501a3f12e90008a
Repo:dpdk, Branch:master, CommitID:3047c857a7edae2a2685c8cd72f15dee9d3c2b22
Apply patch file failed:
Repo: dpdk
24582:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 556.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 succeeded at 354 with fuzz 2 (offset -16 lines).
patching file drivers/net/mlx4/mlx4_flow.c
patching file drivers/net/mlx4/mlx4_flow.h
Hunk #1 succeeded at 93 (offset -4 lines).
Repo: dpdk-next-crypto
24582:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 556.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 succeeded at 354 with fuzz 2 (offset -16 lines).
patching file drivers/net/mlx4/mlx4_flow.c
patching file drivers/net/mlx4/mlx4_flow.h
Hunk #1 succeeded at 93 (offset -4 lines).
Repo: dpdk-next-net
24582:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 556.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 succeeded at 354 with fuzz 2 (offset -16 lines).
patching file drivers/net/mlx4/mlx4_flow.c
patching file drivers/net/mlx4/mlx4_flow.h
Hunk #1 succeeded at 93 (offset -4 lines).
Repo: dpdk-next-virtio
24582:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 556.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 succeeded at 354 with fuzz 2 (offset -16 lines).
patching file drivers/net/mlx4/mlx4_flow.c
patching file drivers/net/mlx4/mlx4_flow.h
Hunk #1 succeeded at 93 (offset -4 lines).
Repo: dpdk-next-eventdev
24582:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 556.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 succeeded at 354 with fuzz 2 (offset -16 lines).
patching file drivers/net/mlx4/mlx4_flow.c
patching file drivers/net/mlx4/mlx4_flow.h
Hunk #1 succeeded at 93 (offset -4 lines).
DPDK STV team
reply other threads:[~2017-05-26 5:00 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='e81775$12bj4cm@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=vasilyf@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).