From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: mb@smartsharesystems.com, zhoumin@loongson.cn
Subject: |WARNING| pw156092-156091 [PATCH v7 1/3] mbuf: de-inline sanity checking a reinitialized mbuf
Date: Sat, 23 Aug 2025 07:22:18 +0800 [thread overview]
Message-ID: <202508222322.57MNMI00904024@localhost.localdomain> (raw)
In-Reply-To: <20250822234515.22518-2-mb@smartsharesystems.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/156092
_apply patch failure_
Submitter: Morten Brørup <mb@smartsharesystems.com>
Date: Fri, 22 Aug 2025 23:45:13 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 38543d33bd47fc0ee21f59db80a8763620741879
Apply patch set 156092-156091 failed:
Checking patch lib/mbuf/rte_mbuf.h...
error: while searching for:
static inline int rte_pktmbuf_alloc_bulk(struct rte_mempool *pool,
struct rte_mbuf **mbufs, unsigned count)
{
unsigned idx = 0;
int rc;
rc = rte_mbuf_raw_alloc_bulk(pool, (void **)mbufs, count);
if (unlikely(rc))
return rc;
/* To understand duff's device on loop unwinding optimization, see
* https://en.wikipedia.org/wiki/Duff's_device.
* Here while() loop is used rather than do() while{} to avoid extra
* check if count is zero.
*/
switch (count % 4) {
case 0:
while (idx != count) {
rte_pktmbuf_reset(mbufs[idx]);
idx++;
/* fall-through */
case 3:
rte_pktmbuf_reset(mbufs[idx]);
idx++;
/* fall-through */
case 2:
rte_pktmbuf_reset(mbufs[idx]);
idx++;
/* fall-through */
case 1:
rte_pktmbuf_reset(mbufs[idx]);
idx++;
/* fall-through */
}
}
return 0;
}
error: patch failed: lib/mbuf/rte_mbuf.h:1018
error: lib/mbuf/rte_mbuf.h: patch does not apply
next parent reply other threads:[~2025-08-22 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250822234515.22518-2-mb@smartsharesystems.com>
2025-08-22 23:22 ` qemudev [this message]
2025-08-22 23:44 ` |WARNING| pw156092 " 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=202508222322.57MNMI00904024@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=mb@smartsharesystems.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).