automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, Andrew.Boyer@amd.com
Subject: compilation|WARNING| pw(136456) sid(31030) job(PER_PATCH_BUILD10923)[v2, 13/13] net/ionic: optimize device start operation
Date: 06 Feb 2024 23:54:53 -0800	[thread overview]
Message-ID: <97ef63$5j58b@orviesa005-auth.jf.intel.com> (raw)

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


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

_apply issues_

Submitter: Andrew Boyer <Andrew.Boyer@amd.com>
Date: 2024-02-07 02:18:49
Reply_mail: <20240207021849.52988-14-andrew.boyer@amd.com>

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


* Repo: dpdk-next-net
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: drivers/net/ionic/ionic_lif.c:1621
error: drivers/net/ionic/ionic_lif.c: patch does not apply
error: patch failed: drivers/net/ionic/ionic_lif.h:228
error: drivers/net/ionic/ionic_lif.h: patch does not apply
error: patch failed: drivers/net/ionic/ionic_rxtx.h:46
error: drivers/net/ionic/ionic_rxtx.h: patch does not apply
Applying: net/ionic: optimize device start operation
Patch failed at 0001 net/ionic: optimize device start operation
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: drivers/net/ionic/ionic_lif.c:1621
error: drivers/net/ionic/ionic_lif.c: patch does not apply
error: patch failed: drivers/net/ionic/ionic_lif.h:228
error: drivers/net/ionic/ionic_lif.h: patch does not apply
error: patch failed: drivers/net/ionic/ionic_rxtx.h:46
error: drivers/net/ionic/ionic_rxtx.h: patch does not apply
Applying: net/ionic: optimize device start operation
Patch failed at 0001 net/ionic: optimize device start operation
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-07  7:54 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='97ef63$5j58b@orviesa005-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=Andrew.Boyer@amd.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).