automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, alan.elder@microsoft.com
Subject: compilation|WARNING| pw(136534) sid(31051) job(PER_PATCH_BUILD10944)net/netvsc: fix parsing of VLAN metadata
Date: 08 Feb 2024 06:23:02 -0800	[thread overview]
Message-ID: <e80169$1s0ge@fmviesa006-auth.fm.intel.com> (raw)

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


Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/136534

_apply issues_

Submitter: Alan Elder <alan.elder@microsoft.com>
Date: 2024-02-08 14:12:38
Reply_mail: <PA4PR83MB0526398D23186AB50C38D0EF97442@PA4PR83MB0526.EURPRD83.prod.outlook.com>

DPDK git baseline:
	Repo:dpdk-next-net, CommitID: ee647455f04c02ee98f75b6c690dba8cc1027e09
	Repo:dpdk, CommitID: a4ce111cc89f580b8c4aad51bdb061acbdfde86b


* Repo: dpdk-next-net
Now app must provide a service core for each NFP pci device that uses
    flower driver to run flower service, which will cause huge resource waste.
    This patch is to solve this problem and app can only use one core to
    run NFP flower service though it uses several NFP NICs.
    
    Signed-off-by: Long Wu <long.wu@corigine.com>
--
Server version missing
You should provide the server version in the URL configured via git-config or --server
This will be required in git-pw 2.0
error: patch failed: .mailmap:32
error: .mailmap: patch does not apply
error: patch failed: drivers/net/netvsc/hn_rxtx.c:42
error: drivers/net/netvsc/hn_rxtx.c: patch does not apply
error: patch failed: drivers/net/netvsc/ndis.h:316
error: drivers/net/netvsc/ndis.h: patch does not apply
Applying: net/netvsc: fix parsing of VLAN metadata
Patch failed at 0001 net/netvsc: fix parsing of VLAN metadata
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
mem: initialise shared locks explicitly
    
    Locks in the DPDK shared memory were not initialised so far.
    This is not really a problem as the early_mem_config structure is stored
    in the bss section (and so set to 0 by default).
    Yet, for consistency, explicitly initialise those locks with relevant
    initialiser macros.
--
Server version missing
You should provide the server version in the URL configured via git-config or --server
This will be required in git-pw 2.0
error: patch failed: .mailmap:32
error: .mailmap: patch does not apply
error: patch failed: drivers/net/netvsc/hn_rxtx.c:42
error: drivers/net/netvsc/hn_rxtx.c: patch does not apply
error: patch failed: drivers/net/netvsc/ndis.h:316
error: drivers/net/netvsc/ndis.h: patch does not apply
Applying: net/netvsc: fix parsing of VLAN metadata
Patch failed at 0001 net/netvsc: fix parsing of VLAN metadata
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

                 reply	other threads:[~2024-02-08 14:23 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='e80169$1s0ge@fmviesa006-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=alan.elder@microsoft.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).