From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: nelio.laranjeiro@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw29976 [PATCH v3 21/30] net/mlx5: remove hash Rx queues support
Date: 11 Oct 2017 18:19:29 -0700 [thread overview]
Message-ID: <a2ed28$14kr6ea@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3072 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/29976
_apply patch file failure_
Submitter: =?utf-8?q?N=C3=A9lio_Laranjeiro?= <nelio.laranjeiro@6wind.com>
Date: Mon, 9 Oct 2017 16:44:48 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:457f7a1876b56fa254eec1c36f429d62b92734bd
Repo:dpdk-next-crypto, Branch:master, CommitID:f255b48dc3e66ca94c5bd60ce20f68ba0eb7f33e
Repo:dpdk-next-net, Branch:master, CommitID:8ec06fbb82d043e115e5740b90c2e7f937bf004a
Repo:dpdk-next-virtio, Branch:master, CommitID:7fbf963714bf7525a28024c5f54bba2b4b3b1a1f
Repo:dpdk, Branch:master, CommitID:63bdef1827f5a98ab375877cb994ef92c33a0b8a
Apply patch file failed:
Repo: dpdk
29976:
patching file drivers/net/mlx5/mlx5.c
Hunk #1 succeeded at 152 (offset -46 lines).
patching file drivers/net/mlx5/mlx5.h
Hunk #1 succeeded at 132 (offset 5 lines).
patching file drivers/net/mlx5/mlx5_rxq.c
patching file drivers/net/mlx5/mlx5_rxtx.h
Hunk #2 succeeded at 221 (offset -12 lines).
patching file drivers/net/mlx5/mlx5_trigger.c
Hunk #1 FAILED at 161.
Hunk #2 succeeded at 169 (offset -21 lines).
Hunk #3 succeeded at 203 (offset -21 lines).
1 out of 3 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_trigger.c.rej
Repo: dpdk-next-crypto
29976:
patching file drivers/net/mlx5/mlx5.c
Hunk #1 succeeded at 152 (offset -46 lines).
patching file drivers/net/mlx5/mlx5.h
Hunk #1 succeeded at 132 (offset 5 lines).
patching file drivers/net/mlx5/mlx5_rxq.c
patching file drivers/net/mlx5/mlx5_rxtx.h
Hunk #2 succeeded at 221 (offset -12 lines).
patching file drivers/net/mlx5/mlx5_trigger.c
Hunk #1 FAILED at 161.
Hunk #2 succeeded at 169 (offset -21 lines).
Hunk #3 succeeded at 203 (offset -21 lines).
1 out of 3 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_trigger.c.rej
Repo: dpdk-next-virtio
29976:
patching file drivers/net/mlx5/mlx5.c
Hunk #1 succeeded at 152 (offset -46 lines).
patching file drivers/net/mlx5/mlx5.h
Hunk #1 succeeded at 132 (offset 5 lines).
patching file drivers/net/mlx5/mlx5_rxq.c
patching file drivers/net/mlx5/mlx5_rxtx.h
Hunk #2 succeeded at 221 (offset -12 lines).
patching file drivers/net/mlx5/mlx5_trigger.c
Hunk #1 FAILED at 161.
Hunk #2 succeeded at 169 (offset -21 lines).
Hunk #3 succeeded at 203 (offset -21 lines).
1 out of 3 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_trigger.c.rej
Repo: dpdk-next-eventdev
29976:
patching file drivers/net/mlx5/mlx5.c
Hunk #1 succeeded at 152 (offset -46 lines).
patching file drivers/net/mlx5/mlx5.h
Hunk #1 succeeded at 132 (offset 5 lines).
patching file drivers/net/mlx5/mlx5_rxq.c
patching file drivers/net/mlx5/mlx5_rxtx.h
Hunk #2 succeeded at 221 (offset -12 lines).
patching file drivers/net/mlx5/mlx5_trigger.c
Hunk #1 FAILED at 161.
Hunk #2 succeeded at 169 (offset -21 lines).
Hunk #3 succeeded at 203 (offset -21 lines).
1 out of 3 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_trigger.c.rej
DPDK STV team
reply other threads:[~2017-10-12 1:19 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='a2ed28$14kr6ea@fmsmga002.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).