automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: nelio.laranjeiro@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw29957 [PATCH v3 02/30] net/mlx5: remove flow director support
Date: 11 Oct 2017 19:04:19 -0700	[thread overview]
Message-ID: <8a7c36$136c96e@orsmga001.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2278 bytes --]

Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/29957

_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-next-net
29957:
patching file doc/guides/nics/features/mlx5.ini
patching file doc/guides/nics/mlx5.rst
patching file drivers/net/mlx5/Makefile
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/Makefile.rej
patching file drivers/net/mlx5/mlx5.c
Hunk #1 FAILED at 201.
Hunk #2 FAILED at 844.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5.c.rej
patching file drivers/net/mlx5/mlx5.h
Hunk #1 FAILED at 145.
Hunk #2 FAILED at 273.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5.h.rej
The next patch would delete the file drivers/net/mlx5/mlx5_fdir.c,
which does not exist!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
patching file drivers/net/mlx5/mlx5_flow.c
Hunk #1 succeeded at 496 with fuzz 1 (offset 198 lines).
patching file drivers/net/mlx5/mlx5_rxq.c
Hunk #1 FAILED at 760.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx5/mlx5_rxq.c.rej
patching file drivers/net/mlx5/mlx5_rxtx.h
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file drivers/net/mlx5/mlx5_rxtx.h.rej
patching file drivers/net/mlx5/mlx5_trigger.c
Hunk #1 FAILED at 80.
Hunk #2 FAILED at 135.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx5/mlx5_trigger.c.rej


DPDK STV team

                 reply	other threads:[~2017-10-12  2:04 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='8a7c36$136c96e@orsmga001.jf.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).