automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, bruce.richardson@intel.com
Subject: compilation|WARNING| pw(152456) sid(34877) job(PER_PATCH_BUILD15268)[v3, 07/11] acl: use common AVX build handling
Date: 18 Mar 2025 10:43:39 -0700	[thread overview]
Message-ID: <1afc83$3kqptn@fmviesa008-auth.fm.intel.com> (raw)

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


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

_apply issues_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: 2025-03-18 17:35:00
Reply_mail: <20250318173505.314529-8-bruce.richardson@intel.com>

DPDK git baseline:
	Repo:dpdk, CommitID: 44a86bcf2447d7d914d7195448285aa82eaedcba


* Repo: dpdk
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/intel/i40e/meson.build:40
error: drivers/net/intel/i40e/meson.build: patch does not apply
error: patch failed: drivers/net/intel/iavf/meson.build:28
error: drivers/net/intel/iavf/meson.build: patch does not apply
error: patch failed: drivers/net/intel/ice/meson.build:34
error: drivers/net/intel/ice/meson.build: patch does not apply
Applying: build: add generalized AVX handling for drivers
Applying: net/intel: use common AVX build code
Patch failed at 0002 net/intel: use common AVX build code
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:[~2025-03-18 17:43 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='1afc83$3kqptn@fmviesa008-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=bruce.richardson@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).