From: sys_stv@intel.com
To: test-report@dpdk.org, tathagat.dpdk@gmail.com
Subject: compilation|WARNING| pw(142498) sid(32533) job(PER_PATCH_BUILD12628)net/gve: Update Rx/Tx functions for RTE_PROC_SECONDARY
Date: 17 Jul 2024 22:43:07 -0700 [thread overview]
Message-ID: <96072c$1kssln@orviesa005-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/142498
_apply issues_
Submitter: Tathagat Priyadarshi <tathagat.dpdk@gmail.com>
Date: 2024-07-18 05:34:06
Reply_mail: <CA++LmPWP+fAn_uB=mGNuB_9jG16sZc4gTrEpoAm-aUYw8kF70Q@mail.gmail.com>
DPDK git baseline:
Repo:dpdk-next-net, CommitID: d32d6c8e31923c3a1eeebe7da6ded89332830576
Repo:dpdk, CommitID: fa8d2f7f28524a6c8defa3dcd94f5aa131aae084
* Repo: dpdk-next-net
Build errors on some ARM platforms are introduced by this patch:
../drivers/net/ngbe/base/ngbe_mng.c: In function 'ngbe_hic_get_lldp':
../drivers/net/ngbe/base/ngbe_mng.c:127:36: error: array subscript 2
is outside array bounds of 'struct ngbe_hic_write_lldp[1]' [-Werror=
array-bounds]
127 | buffer[bi] = rd32a(hw, NGBE_MNGMBX, bi);
../drivers/net/ngbe/base/ngbe_mng.c:385:36: note: while referencing
--
You should provide the server version in the URL configured via git-config or --server
This will be required in git-pw 2.0
Patch is empty.
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
You should provide the server version in the URL configured via git-config or --server
This will be required in git-pw 2.0
Patch is empty.
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
reply other threads:[~2024-07-18 5:45 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='96072c$1kssln@orviesa005-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=tathagat.dpdk@gmail.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).