From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Rahul Bhansali <rbhansali@marvell.com>, zhoumin@loongson.cn
Subject: |WARNING| pw154633-154634 [PATCH v2 1/2] net/cnxk: fix lock for security session ops
Date: Mon, 23 Jun 2025 20:16:16 +0800 [thread overview]
Message-ID: <202506231216.55NCGGnF1063618@localhost.localdomain> (raw)
In-Reply-To: <20250623044907.2906896-1-rbhansali@marvell.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/154633
_apply patch failure RETEST #1_
Submitter: Rahul Bhansali <rbhansali@marvell.com>
Date: Mon, 23 Jun 2025 10:19:06 +0530
DPDK git baseline: Repo:dpdk-next-net-mrvl
Branch: for-next-net
CommitID: 3408b132b31906fe1ed28d6b2009b98202e1cff0
Apply patch set 154633-154634 failed:
Checking patch drivers/net/cnxk/cn10k_ethdev_sec.c...
error: while searching for:
inbound = !!(ipsec->direction == RTE_SECURITY_IPSEC_SA_DIR_INGRESS);
inl_dev = !!dev->inb.inl_dev;
memset(eth_sec, 0, sizeof(struct cnxk_eth_sec_sess));
sess_priv.u64 = 0;
lock = inbound ? &dev->inb.lock : &dev->outb.lock;
error: patch failed: drivers/net/cnxk/cn10k_ethdev_sec.c:786
error: drivers/net/cnxk/cn10k_ethdev_sec.c: patch does not apply
Checking patch drivers/net/cnxk/cnxk_ethdev_sec.c...
error: while searching for:
{
struct rte_eth_dev *eth_dev = &rte_eth_devices[portid];
struct cnxk_eth_dev *dev = cnxk_eth_pmd_priv(eth_dev);
return roc_nix_inl_sa_sync(&dev->nix, sess, inb, ROC_NIX_INL_SA_OP_FLUSH);
}
RTE_EXPORT_EXPERIMENTAL_SYMBOL(rte_pmd_cnxk_hw_sa_read, 22.07)
error: patch failed: drivers/net/cnxk/cnxk_ethdev_sec.c:354
error: drivers/net/cnxk/cnxk_ethdev_sec.c: patch does not apply
next prev parent reply other threads:[~2025-06-23 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250623044907.2906896-1-rbhansali@marvell.com>
2025-06-23 4:49 ` |SUCCESS| pw154633 " checkpatch
2025-06-23 12:16 ` qemudev [this message]
2025-06-23 12:26 ` |WARNING| pw154633-154634 " qemudev
2025-06-23 12:40 ` qemudev
2025-06-23 13:27 ` qemudev
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=202506231216.55NCGGnF1063618@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=rbhansali@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).