From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Zhuobin Huang <zobin1999@gmail.com>, zhoumin@loongson.cn
Subject: |WARNING| pw124805 [PATCH v2] app/test: fix data length of each packet segment
Date: Mon, 6 Mar 2023 14:59:16 +0800 [thread overview]
Message-ID: <202303060659.3266xGs83955882@localhost.localdomain> (raw)
In-Reply-To: <20230305205144.14443-1-zobin1999@gmail.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/124805
_apply patch failure_
Submitter: Zhuobin Huang <zobin1999@gmail.com>
Date: Mon, 6 Mar 2023 04:51:44 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
Apply patch set 124805 failed:
/home/zhoumin/dpdk-ci/tools/../series/27251/124805.patch:119: space before tab in indent.
struct rte_mbuf *pkt_seg;
/home/zhoumin/dpdk-ci/tools/../series/27251/124805.patch:120: space before tab in indent.
struct rte_mbuf *pkt;
/home/zhoumin/dpdk-ci/tools/../series/27251/124805.patch:121: trailing whitespace.
/home/zhoumin/dpdk-ci/tools/../series/27251/124805.patch:124: space before tab in indent.
for (nb_pkt = 0; nb_pkt < nb_pkt_per_burst; nb_pkt++) {
/home/zhoumin/dpdk-ci/tools/../series/27251/124805.patch:125: space before tab in indent.
pkt = rte_pktmbuf_alloc(mp);
Checking patch 0001-app-test-fix-data-length-of-each-packet-segment.patch...
Checking patch app/test/packet_burst_generator.c...
error: while searching for:
goto nomore_mbuf;
}
pkt_seg = pkt_seg->next;
if(i != nb_pkt_segs - 1)
pkt_seg->data_len = pkt_seg_data_len;
else
pkt_seg->data_len = pkt_seg_data_len + pkt_len % nb_pkt_segs;
error: patch failed: app/test/packet_burst_generator.c:371
error: app/test/packet_burst_generator.c: patch does not apply
prev parent reply other threads:[~2023-03-06 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230305205144.14443-1-zobin1999@gmail.com>
2023-03-05 20:53 ` checkpatch
2023-03-06 6:59 ` qemudev [this message]
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=202303060659.3266xGs83955882@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=test-report@dpdk.org \
--cc=zhoumin@loongson.cn \
--cc=zobin1999@gmail.com \
/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).