From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: ajit.khaparde@broadcom.com
Subject: [dpdk-test-report] |FAILURE| pw24930 [PATCH v3 21/26] net/bnxt: add support to get and clear VF specific stats
Date: 01 Jun 2017 14:36:43 -0700 [thread overview]
Message-ID: <e81775$12e0u3r@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 10119 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/24930
_apply patch file failure_
Submitter: Ajit Khaparde <ajit.khaparde@broadcom.com>
Date: Wed, 31 May 2017 22:02:27 -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
24930:
patching file app/test-pmd/cmdline.c
Hunk #1 succeeded at 13042 (offset -37 lines).
Hunk #2 succeeded at 13147 (offset -37 lines).
patching file drivers/net/bnxt/bnxt_hwrm.c
Hunk #1 FAILED at 1237.
Hunk #2 succeeded at 956 (offset -318 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt_hwrm.c.rej
patching file drivers/net/bnxt/bnxt_hwrm.h
Hunk #1 FAILED at 66.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/bnxt/bnxt_hwrm.h.rej
patching file drivers/net/bnxt/bnxt_stats.c
Hunk #1 succeeded at 43 with fuzz 2 (offset -122 lines).
Hunk #2 FAILED at 267.
Hunk #3 FAILED at 274.
Hunk #4 FAILED at 298.
Hunk #5 FAILED at 305.
Hunk #6 FAILED at 327.
5 out of 6 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt_stats.c.rej
can't find file to patch at input line 225
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/bnxt/rte_pmd_bnxt.c b/drivers/net/bnxt/rte_pmd_bnxt.c
|index 4a714b1..d9e97ab 100644
|--- a/drivers/net/bnxt/rte_pmd_bnxt.c
|+++ b/drivers/net/bnxt/rte_pmd_bnxt.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 316
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/bnxt/rte_pmd_bnxt.h b/drivers/net/bnxt/rte_pmd_bnxt.h
|index b9176cd..eef5212 100644
|--- a/drivers/net/bnxt/rte_pmd_bnxt.h
|+++ b/drivers/net/bnxt/rte_pmd_bnxt.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/net/bnxt/rte_pmd_bnxt_version.map
Hunk #1 FAILED at 9.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/bnxt/rte_pmd_bnxt_version.map.rej
Repo: dpdk-next-crypto
24930:
patching file app/test-pmd/cmdline.c
Hunk #1 succeeded at 13042 (offset -37 lines).
Hunk #2 succeeded at 13147 (offset -37 lines).
patching file drivers/net/bnxt/bnxt_hwrm.c
Hunk #1 FAILED at 1237.
Hunk #2 succeeded at 956 (offset -318 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt_hwrm.c.rej
patching file drivers/net/bnxt/bnxt_hwrm.h
Hunk #1 FAILED at 66.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/bnxt/bnxt_hwrm.h.rej
patching file drivers/net/bnxt/bnxt_stats.c
Hunk #1 succeeded at 43 with fuzz 2 (offset -122 lines).
Hunk #2 FAILED at 267.
Hunk #3 FAILED at 274.
Hunk #4 FAILED at 298.
Hunk #5 FAILED at 305.
Hunk #6 FAILED at 327.
5 out of 6 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt_stats.c.rej
can't find file to patch at input line 225
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/bnxt/rte_pmd_bnxt.c b/drivers/net/bnxt/rte_pmd_bnxt.c
|index 4a714b1..d9e97ab 100644
|--- a/drivers/net/bnxt/rte_pmd_bnxt.c
|+++ b/drivers/net/bnxt/rte_pmd_bnxt.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 316
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/bnxt/rte_pmd_bnxt.h b/drivers/net/bnxt/rte_pmd_bnxt.h
|index b9176cd..eef5212 100644
|--- a/drivers/net/bnxt/rte_pmd_bnxt.h
|+++ b/drivers/net/bnxt/rte_pmd_bnxt.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/net/bnxt/rte_pmd_bnxt_version.map
Hunk #1 FAILED at 9.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/bnxt/rte_pmd_bnxt_version.map.rej
Repo: dpdk-next-net
24930:
patching file app/test-pmd/cmdline.c
Hunk #1 succeeded at 13057 (offset -22 lines).
Hunk #2 succeeded at 13162 (offset -22 lines).
patching file drivers/net/bnxt/bnxt_hwrm.c
Hunk #1 FAILED at 1237.
Hunk #2 succeeded at 956 (offset -318 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt_hwrm.c.rej
patching file drivers/net/bnxt/bnxt_hwrm.h
Hunk #1 FAILED at 66.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/bnxt/bnxt_hwrm.h.rej
patching file drivers/net/bnxt/bnxt_stats.c
Hunk #1 succeeded at 43 with fuzz 2 (offset -122 lines).
Hunk #2 FAILED at 267.
Hunk #3 FAILED at 274.
Hunk #4 FAILED at 298.
Hunk #5 FAILED at 305.
Hunk #6 FAILED at 327.
5 out of 6 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt_stats.c.rej
can't find file to patch at input line 225
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/bnxt/rte_pmd_bnxt.c b/drivers/net/bnxt/rte_pmd_bnxt.c
|index 4a714b1..d9e97ab 100644
|--- a/drivers/net/bnxt/rte_pmd_bnxt.c
|+++ b/drivers/net/bnxt/rte_pmd_bnxt.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 316
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/bnxt/rte_pmd_bnxt.h b/drivers/net/bnxt/rte_pmd_bnxt.h
|index b9176cd..eef5212 100644
|--- a/drivers/net/bnxt/rte_pmd_bnxt.h
|+++ b/drivers/net/bnxt/rte_pmd_bnxt.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/net/bnxt/rte_pmd_bnxt_version.map
Hunk #1 FAILED at 9.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/bnxt/rte_pmd_bnxt_version.map.rej
Repo: dpdk-next-virtio
24930:
patching file app/test-pmd/cmdline.c
Hunk #1 succeeded at 13042 (offset -37 lines).
Hunk #2 succeeded at 13147 (offset -37 lines).
patching file drivers/net/bnxt/bnxt_hwrm.c
Hunk #1 FAILED at 1237.
Hunk #2 succeeded at 956 (offset -318 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt_hwrm.c.rej
patching file drivers/net/bnxt/bnxt_hwrm.h
Hunk #1 FAILED at 66.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/bnxt/bnxt_hwrm.h.rej
patching file drivers/net/bnxt/bnxt_stats.c
Hunk #1 succeeded at 43 with fuzz 2 (offset -122 lines).
Hunk #2 FAILED at 267.
Hunk #3 FAILED at 274.
Hunk #4 FAILED at 298.
Hunk #5 FAILED at 305.
Hunk #6 FAILED at 327.
5 out of 6 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt_stats.c.rej
can't find file to patch at input line 225
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/bnxt/rte_pmd_bnxt.c b/drivers/net/bnxt/rte_pmd_bnxt.c
|index 4a714b1..d9e97ab 100644
|--- a/drivers/net/bnxt/rte_pmd_bnxt.c
|+++ b/drivers/net/bnxt/rte_pmd_bnxt.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 316
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/bnxt/rte_pmd_bnxt.h b/drivers/net/bnxt/rte_pmd_bnxt.h
|index b9176cd..eef5212 100644
|--- a/drivers/net/bnxt/rte_pmd_bnxt.h
|+++ b/drivers/net/bnxt/rte_pmd_bnxt.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/net/bnxt/rte_pmd_bnxt_version.map
Hunk #1 FAILED at 9.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/bnxt/rte_pmd_bnxt_version.map.rej
Repo: dpdk-next-eventdev
24930:
patching file app/test-pmd/cmdline.c
Hunk #1 succeeded at 13042 (offset -37 lines).
Hunk #2 succeeded at 13147 (offset -37 lines).
patching file drivers/net/bnxt/bnxt_hwrm.c
Hunk #1 FAILED at 1237.
Hunk #2 succeeded at 956 (offset -318 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt_hwrm.c.rej
patching file drivers/net/bnxt/bnxt_hwrm.h
Hunk #1 FAILED at 66.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/bnxt/bnxt_hwrm.h.rej
patching file drivers/net/bnxt/bnxt_stats.c
Hunk #1 succeeded at 43 with fuzz 2 (offset -122 lines).
Hunk #2 FAILED at 267.
Hunk #3 FAILED at 274.
Hunk #4 FAILED at 298.
Hunk #5 FAILED at 305.
Hunk #6 FAILED at 327.
5 out of 6 hunks FAILED -- saving rejects to file drivers/net/bnxt/bnxt_stats.c.rej
can't find file to patch at input line 225
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/bnxt/rte_pmd_bnxt.c b/drivers/net/bnxt/rte_pmd_bnxt.c
|index 4a714b1..d9e97ab 100644
|--- a/drivers/net/bnxt/rte_pmd_bnxt.c
|+++ b/drivers/net/bnxt/rte_pmd_bnxt.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 316
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/net/bnxt/rte_pmd_bnxt.h b/drivers/net/bnxt/rte_pmd_bnxt.h
|index b9176cd..eef5212 100644
|--- a/drivers/net/bnxt/rte_pmd_bnxt.h
|+++ b/drivers/net/bnxt/rte_pmd_bnxt.h
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/net/bnxt/rte_pmd_bnxt_version.map
Hunk #1 FAILED at 9.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/bnxt/rte_pmd_bnxt_version.map.rej
DPDK STV team
reply other threads:[~2017-06-01 21:36 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$12e0u3r@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).