[dpdk-test-report] |FAILURE| pw24918 [PATCH v3 09/26] net/bnxt: add support for set multicast addr list and MAC addr set

automatic DPDK test reports
 help / color / mirror / Atom feed

From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: ajit.khaparde@broadcom.com
Subject: [dpdk-test-report] |FAILURE| pw24918 [PATCH v3 09/26] net/bnxt: add support for set multicast addr list and MAC addr set
Date: 01 Jun 2017 08:28:18 -0700	[thread overview]
Message-ID: <e81775$12dsi4f@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Ajit Khaparde <ajit.khaparde@broadcom.com>
Date: Wed, 31 May 2017 22:02:15 -0500
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7021fcbb2f5a4fc3e32f2bfd1a27f3dc671d3476
                   Repo:dpdk-next-crypto, Branch:master, CommitID:bc6ebd8c3e7391d3d0d909a9a068caf0f2171103
                   Repo:dpdk-next-net, Branch:master, CommitID:9b0a01bdd2ff38efc7cd83d65e7e071aebe712f5
                   Repo:dpdk-next-virtio, Branch:master, CommitID:1ee9702c260bbd4a282efdeaa7277ddbfc87177a
                   Repo:dpdk, Branch:master, CommitID:3047c857a7edae2a2685c8cd72f15dee9d3c2b22
                   
Apply patch file failed:
Repo: dpdk
24918:
patching file drivers/net/bnxt/bnxt_ethdev.c
Hunk #1 succeeded at 651 (offset 13 lines).
Hunk #2 FAILED at 1155.
Hunk #3 FAILED at 1229.
Hunk #4 succeeded at 1003 with fuzz 1 (offset -287 lines).
Hunk #5 FAILED at 1391.
3 out of 5 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt_ethdev.c.rej
patching file drivers/net/bnxt/bnxt_hwrm.c
Hunk #1 succeeded at 178 (offset -51 lines).
Hunk #2 succeeded at 215 (offset -51 lines).
Hunk #3 succeeded at 229 (offset -51 lines).
Hunk #4 succeeded at 1206 (offset -218 lines).
patching file drivers/net/bnxt/bnxt_hwrm.h
Hunk #1 succeeded at 49 with fuzz 2.
patching file drivers/net/bnxt/bnxt_vnic.c
Hunk #1 succeeded at 177 with fuzz 1 (offset 7 lines).
Hunk #2 succeeded at 220 (offset 1 line).
patching file drivers/net/bnxt/bnxt_vnic.h
Hunk #1 succeeded at 56 (offset -1 lines).

Repo: dpdk-next-crypto
24918:
patching file drivers/net/bnxt/bnxt_ethdev.c
Hunk #1 succeeded at 651 (offset 13 lines).
Hunk #2 FAILED at 1155.
Hunk #3 FAILED at 1229.
Hunk #4 succeeded at 1003 with fuzz 1 (offset -287 lines).
Hunk #5 FAILED at 1391.
3 out of 5 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt_ethdev.c.rej
patching file drivers/net/bnxt/bnxt_hwrm.c
Hunk #1 succeeded at 178 (offset -51 lines).
Hunk #2 succeeded at 215 (offset -51 lines).
Hunk #3 succeeded at 229 (offset -51 lines).
Hunk #4 succeeded at 1206 (offset -218 lines).
patching file drivers/net/bnxt/bnxt_hwrm.h
Hunk #1 succeeded at 49 with fuzz 2.
patching file drivers/net/bnxt/bnxt_vnic.c
Hunk #1 succeeded at 177 with fuzz 1 (offset 7 lines).
Hunk #2 succeeded at 220 (offset 1 line).
patching file drivers/net/bnxt/bnxt_vnic.h
Hunk #1 succeeded at 56 (offset -1 lines).

Repo: dpdk-next-net
24918:
patching file drivers/net/bnxt/bnxt_ethdev.c
Hunk #1 succeeded at 651 (offset 13 lines).
Hunk #2 FAILED at 1155.
Hunk #3 FAILED at 1229.
Hunk #4 succeeded at 1003 with fuzz 1 (offset -287 lines).
Hunk #5 FAILED at 1391.
3 out of 5 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt_ethdev.c.rej
patching file drivers/net/bnxt/bnxt_hwrm.c
Hunk #1 succeeded at 178 (offset -51 lines).
Hunk #2 succeeded at 215 (offset -51 lines).
Hunk #3 succeeded at 229 (offset -51 lines).
Hunk #4 succeeded at 1206 (offset -218 lines).
patching file drivers/net/bnxt/bnxt_hwrm.h
Hunk #1 succeeded at 49 with fuzz 2.
patching file drivers/net/bnxt/bnxt_vnic.c
Hunk #1 succeeded at 177 with fuzz 1 (offset 7 lines).
Hunk #2 succeeded at 220 (offset 1 line).
patching file drivers/net/bnxt/bnxt_vnic.h
Hunk #1 succeeded at 56 (offset -1 lines).

Repo: dpdk-next-virtio
24918:
patching file drivers/net/bnxt/bnxt_ethdev.c
Hunk #1 succeeded at 651 (offset 13 lines).
Hunk #2 FAILED at 1155.
Hunk #3 FAILED at 1229.
Hunk #4 succeeded at 1003 with fuzz 1 (offset -287 lines).
Hunk #5 FAILED at 1391.
3 out of 5 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt_ethdev.c.rej
patching file drivers/net/bnxt/bnxt_hwrm.c
Hunk #1 succeeded at 178 (offset -51 lines).
Hunk #2 succeeded at 215 (offset -51 lines).
Hunk #3 succeeded at 229 (offset -51 lines).
Hunk #4 succeeded at 1206 (offset -218 lines).
patching file drivers/net/bnxt/bnxt_hwrm.h
Hunk #1 succeeded at 49 with fuzz 2.
patching file drivers/net/bnxt/bnxt_vnic.c
Hunk #1 succeeded at 177 with fuzz 1 (offset 7 lines).
Hunk #2 succeeded at 220 (offset 1 line).
patching file drivers/net/bnxt/bnxt_vnic.h
Hunk #1 succeeded at 56 (offset -1 lines).

Repo: dpdk-next-eventdev
24918:
patching file drivers/net/bnxt/bnxt_ethdev.c
Hunk #1 succeeded at 651 (offset 13 lines).
Hunk #2 FAILED at 1155.
Hunk #3 FAILED at 1229.
Hunk #4 succeeded at 1003 with fuzz 1 (offset -287 lines).
Hunk #5 FAILED at 1391.
3 out of 5 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt_ethdev.c.rej
patching file drivers/net/bnxt/bnxt_hwrm.c
Hunk #1 succeeded at 178 (offset -51 lines).
Hunk #2 succeeded at 215 (offset -51 lines).
Hunk #3 succeeded at 229 (offset -51 lines).
Hunk #4 succeeded at 1206 (offset -218 lines).
patching file drivers/net/bnxt/bnxt_hwrm.h
Hunk #1 succeeded at 49 with fuzz 2.
patching file drivers/net/bnxt/bnxt_vnic.c
Hunk #1 succeeded at 177 with fuzz 1 (offset 7 lines).
Hunk #2 succeeded at 220 (offset 1 line).
patching file drivers/net/bnxt/bnxt_vnic.h
Hunk #1 succeeded at 56 (offset -1 lines).


DPDK STV team

                 reply	other threads:[~2017-06-01 15:28 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$12dsi4f@fmsmga001.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=ajit.khaparde@broadcom.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).