From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |WARNING| pw(93600) sid(17164) [v2, 2/2] net/bnxt: workaround for spurious zero counter values in Thor
Date: 01 Jun 2021 10:03:04 -0700 [thread overview]
Message-ID: <f381f8$e94qq5@orsmga001-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1902 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/93600
_apply issues_
Submitter: Somnath Kotur <somnath.kotur@broadcom.com>
Date: 2021-05-31 05:53:01
Reply_mail: 20210531055301.28242-1-somnath.kotur@broadcom.com
DPDK git baseline:
Repo:dpdk-next-net-brcm, CommitID: 0ee599933ab55fdac3127b73b3ee87f4d503421a
Repo:dpdk, CommitID: 66b3a54b9feab193a5cf8ad54606d745078587cc
* Repo: dpdk-next-net-brcm
This will be required in git-pw 2.0
Starting new HTTP connection (1): proxy-shz.intel.com
Starting new HTTP connection (1): proxy-shz.intel.com
error: patch failed: drivers/net/bnxt/bnxt_hwrm.h:168
error: drivers/net/bnxt/bnxt_hwrm.h: patch does not apply
error: patch failed: drivers/net/bnxt/bnxt_stats.c:527
error: drivers/net/bnxt/bnxt_stats.c: patch does not apply
Applying: net/bnxt: workaround for spurious zero counter values in Thor
Patch failed at 0001 net/bnxt: workaround for spurious zero counter values in Thor
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
* Repo: dpdk
This will be required in git-pw 2.0
Starting new HTTP connection (1): proxy-shz.intel.com
Starting new HTTP connection (1): proxy-shz.intel.com
error: patch failed: drivers/net/bnxt/bnxt_hwrm.h:302
error: drivers/net/bnxt/bnxt_hwrm.h: patch does not apply
Applying: net/bnxt: workaround for spurious zero counter values in Thor
Patch failed at 0001 net/bnxt: workaround for spurious zero counter values in Thor
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
DPDK STV team
next reply other threads:[~2021-06-01 17:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 17:03 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-03 1:03 sys_stv
2021-06-02 17:03 sys_stv
2021-06-02 9:03 sys_stv
2021-06-02 1:03 sys_stv
2021-06-01 13:06 sys_stv
2021-06-01 9:03 sys_stv
2021-06-01 1:03 sys_stv
2021-05-31 17:03 sys_stv
2021-05-31 10:57 sys_stv
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='f381f8$e94qq5@orsmga001-auth.jf.intel.com' \
--to=sys_stv@intel.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).