From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Tejasree Kondoj <ktejasree@marvell.com>, zhoumin@loongson.cn
Subject: |WARNING| pw153772-153781 [PATCH 1/9] crypto/cnxk: include required headers
Date: Tue, 27 May 2025 20:27:31 +0800 [thread overview]
Message-ID: <202505271227.54RCRVgc2431736@localhost.localdomain> (raw)
In-Reply-To: <20250527130135.2301726-2-ktejasree@marvell.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/153772
_apply patch failure_
Submitter: Tejasree Kondoj <ktejasree@marvell.com>
Date: Tue, 27 May 2025 18:31:27 +0530
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: fc627d7065ba5100faa928cf2edfa1622846f542
Apply patch set 153772-153781 failed:
Checking patch drivers/common/cnxk/roc_cpt_sg.h...
error: while searching for:
#define ROC_SG_MAX_COMP 25
#define ROC_SG_MAX_DLEN_SIZE (ROC_SG_LIST_HDR_SIZE + (ROC_SG_MAX_COMP * ROC_SG_ENTRY_SIZE))
#define ROC_SG2_MAX_PTRS 48
struct roc_sglist_comp {
union {
error: patch failed: drivers/common/cnxk/roc_cpt_sg.h:15
error: drivers/common/cnxk/roc_cpt_sg.h: patch does not apply
Checking patch drivers/crypto/cnxk/cn10k_ipsec_la_ops.h...
Hunk #2 succeeded at 224 (offset -5 lines).
Checking patch drivers/crypto/cnxk/cn10k_tls_ops.h...
Hunk #2 succeeded at 255 (offset -5 lines).
Checking patch drivers/crypto/cnxk/cn20k_ipsec_la_ops.h...
error: drivers/crypto/cnxk/cn20k_ipsec_la_ops.h: No such file or directory
Checking patch drivers/crypto/cnxk/cn20k_tls_ops.h...
error: drivers/crypto/cnxk/cn20k_tls_ops.h: No such file or directory
Checking patch drivers/crypto/cnxk/cn9k_ipsec_la_ops.h...
Hunk #2 succeeded at 214 (offset 3 lines).
next parent reply other threads:[~2025-05-27 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250527130135.2301726-2-ktejasree@marvell.com>
2025-05-27 12:27 ` qemudev [this message]
2025-05-27 13:02 ` |SUCCESS| pw153772 " checkpatch
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=202505271227.54RCRVgc2431736@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=ktejasree@marvell.com \
--cc=test-report@dpdk.org \
--cc=zhoumin@loongson.cn \
/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).