From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Yasin CANER <yasinncaner@gmail.com>, zhoumin@loongson.cn
Subject: |WARNING| pw126880 [PATCH v2] lib/kni : coding style is fixed
Date: Tue, 16 May 2023 18:51:39 +0800 [thread overview]
Message-ID: <202305161051.34GApdsB601094@localhost.localdomain> (raw)
In-Reply-To: <20230516110359.479441-1-yasinncaner@gmail.com>
Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/126880
_apply patch failure_
Submitter: Yasin CANER <yasinncaner@gmail.com>
Date: Tue, 16 May 2023 11:03:59 +0000
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 29f4afc8f28fc532d64f35cccd0bb41853d67f68
Apply patch set 126880 failed:
/home/zhoumin/dpdk-ci/tools/../series/28007/126880.patch:108: trailing whitespace.
/* First, getting allocation count from alloc_q. alloc_q is allocated in this function*/
Checking patch lib/kni/rte_kni.c...
error: while searching for:
RTE_LOG(ERR, KNI, "No valid mempool for allocating mbufs\n");
return;
}
/* First, getting allocation count from alloc_q. alloc_q is allocated in this function
* and/or kni_alloc function from mempool.
* If alloc_q is completely removed, it shall be allocated again.
* */
allocq = kni_fifo_count(kni->alloc_q);
/* How many free allocation is possible from mempool. */
allocq_free = kni_fifo_free_count(kni->alloc_q);
/* Allocated alloc_q count shall be max MAX_MBUF_BURST_NUM. */
allocq_count = MAX_MBUF_BURST_NUM - (int)allocq;
/* Try to figure out how many allocation is possible. allocq_free is max possible.*/
allocq_free = (allocq_free > MAX_MBUF_BURST_NUM )? MAX_MBUF_BURST_NUM : allocq_free;
/* Buffer is not removed so no need re-allocate*/
if(!allocq_count) {
/* Buffer is not removed so no need re-allocation*/
return;
} else if (allocq_free > allocq_count) {
error: patch failed: lib/kni/rte_kni.c:683
error: lib/kni/rte_kni.c: patch does not apply
next parent reply other threads:[~2023-05-16 11:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230516110359.479441-1-yasinncaner@gmail.com>
2023-05-16 10:51 ` qemudev [this message]
2023-05-16 11:04 ` checkpatch
2023-05-16 11:17 |WARNING| pw126880 [PATCH] [v2] " dpdklab
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=202305161051.34GApdsB601094@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=test-report@dpdk.org \
--cc=yasinncaner@gmail.com \
--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).