From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: adrien.mazarguil@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw38510 [PATCH v5 10/16] ethdev: refine TPID handling in flow API
Date: 02 May 2018 20:05:20 -0700 [thread overview]
Message-ID: <0590c7$1iab66@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2183 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38510
_apply patch file failure_
Submitter: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Date: Thu, 19 Apr 2018 12:16:43 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fcde84b5f85b3c1a5d5564299fd49c58ca20370d
Repo:dpdk-next-crypto, Branch:master, CommitID:211992f3b7df5d6d8f1dbefc48bc37a6d5398fbc
Repo:dpdk-next-net, Branch:master, CommitID:36decb6967e0563430a6e3ab0e2db3fe4ccc8db2
Repo:dpdk-next-virtio, Branch:master, CommitID:81daf0ba4f2eb20c00975b474cb9b6ab71c44e25
Repo:dpdk, Branch:master, CommitID:7baac775945ce26f4740158656965f095dc4dbda
Apply patch file failed:
Repo: dpdk-next-virtio
38510:
patching file app/test-pmd/cmdline_flow.c
Hunk #2 succeeded at 481 (offset -24 lines).
Hunk #3 succeeded at 1102 (offset -40 lines).
Hunk #4 succeeded at 1129 (offset -40 lines).
patching file doc/guides/nics/tap.rst
patching file doc/guides/prog_guide/rte_flow.rst
patching file doc/guides/testpmd_app_ug/testpmd_funcs.rst
patching file drivers/net/bnxt/bnxt_filter.c
Hunk #1 succeeded at 298 (offset -9 lines).
Hunk #2 succeeded at 308 (offset -9 lines).
Hunk #3 FAILED at 389.
1 out of 3 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt_filter.c.rej
patching file drivers/net/enic/enic_flow.c
patching file drivers/net/i40e/i40e_flow.c
patching file drivers/net/ixgbe/ixgbe_ethdev.c
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 FAILED at 18.
Hunk #2 succeeded at 304 (offset -2 lines).
Hunk #3 succeeded at 1251 (offset -35 lines).
Hunk #4 succeeded at 1273 (offset -35 lines).
1 out of 4 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_flow.c.rej
patching file drivers/net/mvpp2/mrvl_flow.c
patching file drivers/net/sfc/sfc_flow.c
patching file drivers/net/tap/tap_flow.c
patching file lib/librte_ether/rte_flow.h
Hunk #1 succeeded at 451 (offset -3 lines).
Hunk #2 succeeded at 478 (offset -3 lines).
Hunk #3 succeeded at 640 (offset -3 lines).
Hunk #4 succeeded at 654 (offset -3 lines).
patching file lib/librte_net/rte_ether.h
DPDK STV team
reply other threads:[~2018-05-03 3:05 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='0590c7$1iab66@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=adrien.mazarguil@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).