automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, arkadiuszx.kusztal@intel.com
Subject: compilation|WARNING| pw(137681) sid(31336) job(PER_PATCH_BUILD11240)[v5, 3/3] common/qat: fix incorrectly placed legacy flag
Date: 01 Mar 2024 08:03:36 -0800	[thread overview]
Message-ID: <e669be$87d2p@orviesa007-auth.jf.intel.com> (raw)

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


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

_apply issues_

Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: 2024-03-01 15:52:51
Reply_mail: <20240301155251.5101-3-arkadiuszx.kusztal@intel.com>

DPDK git baseline:
	Repo:dpdk-next-crypto, CommitID: 5ac50824383c2683c0dfdf24c6dc493f1fa54852
	Repo:dpdk, CommitID: 5df34de5808a7b826b8bc035d6ee3161a12be364


* Repo: dpdk-next-crypto
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/compress/qat/qat_comp_pmd.c:683
error: drivers/compress/qat/qat_comp_pmd.c: patch does not apply
error: patch failed: drivers/crypto/qat/qat_asym.c:1515
error: drivers/crypto/qat/qat_asym.c: patch does not apply
error: patch failed: drivers/crypto/qat/qat_sym.c:210
error: drivers/crypto/qat/qat_sym.c: patch does not apply
Applying: common/qat: isolate parser arguments configuration
Patch failed at 0001 common/qat: isolate parser arguments configuration
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
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/common/qat/qat_device.c:231
error: drivers/common/qat/qat_device.c: patch does not apply
error: patch failed: drivers/common/qat/qat_device.h:137
error: drivers/common/qat/qat_device.h: patch does not apply
error: patch failed: drivers/compress/qat/qat_comp_pmd.c:683
error: drivers/compress/qat/qat_comp_pmd.c: patch does not apply
error: patch failed: drivers/crypto/qat/qat_asym.c:1515
error: drivers/crypto/qat/qat_asym.c: patch does not apply
error: patch failed: drivers/crypto/qat/qat_sym.c:210
error: drivers/crypto/qat/qat_sym.c: patch does not apply
Applying: common/qat: isolate parser arguments configuration
Patch failed at 0001 common/qat: isolate parser arguments configuration
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-03-01 16:03 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='e669be$87d2p@orviesa007-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=arkadiuszx.kusztal@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).