From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Shaiq Wani <shaiq.wani@intel.com>
Subject: |WARNING| pw152348 [PATCH] net/intel: using common functions in idpf driver
Date: Wed, 12 Mar 2025 16:52:34 +0100 (CET) [thread overview]
Message-ID: <20250312155234.40292123FC4@dpdk.org> (raw)
In-Reply-To: <20250312155351.409879-1-shaiq.wani@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/152348
_coding style issues_
CHECK:MULTIPLE_ASSIGNMENTS: multiple assignments should be avoided
#1051: FILE: drivers/net/intel/idpf/idpf_common_rxtx_avx2.c:577:
+ nb_commit = nb_pkts = (uint16_t)RTE_MIN(txq->nb_tx_free, nb_pkts);
CHECK:MULTIPLE_ASSIGNMENTS: multiple assignments should be avoided
#1332: FILE: drivers/net/intel/idpf/idpf_common_rxtx_avx512.c:1511:
+ nb_commit = nb_pkts = (uint16_t)RTE_MIN(txq->nb_tx_free, nb_pkts);
total: 0 errors, 0 warnings, 2 checks, 1480 lines checked
next prev parent reply other threads:[~2025-03-12 15:52 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250312155351.409879-1-shaiq.wani@intel.com>
2025-03-12 15:29 ` |SUCCESS| " qemudev
2025-03-12 15:33 ` qemudev
2025-03-12 15:52 ` checkpatch [this message]
2025-03-12 16:57 ` |SUCCESS| pw152348 [PATCH] net/intel: using common functions in idpf dpdklab
2025-03-12 17:00 ` dpdklab
2025-03-12 17:05 ` |SUCCESS| pw152348 [PATCH] net/intel: using common functions in idpf driver 0-day Robot
2025-03-12 17:15 ` |SUCCESS| pw152348 [PATCH] net/intel: using common functions in idpf dpdklab
2025-03-12 17:17 ` dpdklab
2025-03-12 17:22 ` dpdklab
2025-03-12 17:24 ` dpdklab
2025-03-12 17:35 ` dpdklab
2025-03-12 17:36 ` |PENDING| " dpdklab
2025-03-12 18:18 ` dpdklab
2025-03-12 18:24 ` |SUCCESS| " dpdklab
2025-03-12 18:24 ` dpdklab
2025-03-12 18:32 ` dpdklab
2025-03-12 18:34 ` dpdklab
2025-03-12 19:15 ` dpdklab
2025-03-12 20:04 ` dpdklab
2025-03-12 20:11 ` dpdklab
2025-03-12 21:55 ` dpdklab
2025-03-12 21:55 ` |FAILURE| " dpdklab
2025-03-12 21:55 ` |SUCCESS| " dpdklab
2025-03-12 21:59 ` |FAILURE| " dpdklab
2025-03-12 22:07 ` |SUCCESS| " dpdklab
2025-03-12 22:08 ` |FAILURE| " dpdklab
2025-03-12 22:14 ` |PENDING| " dpdklab
2025-03-12 22:18 ` |SUCCESS| " dpdklab
2025-03-12 22:30 ` dpdklab
2025-03-12 23:00 ` dpdklab
2025-03-12 23:11 ` dpdklab
2025-03-12 23:13 ` |PENDING| " dpdklab
2025-03-12 23:24 ` |SUCCESS| " dpdklab
2025-03-12 23:25 ` dpdklab
2025-03-12 23:25 ` dpdklab
2025-03-12 23:45 ` dpdklab
2025-03-12 23:53 ` 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=20250312155234.40292123FC4@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=shaiq.wani@intel.com \
--cc=test-report@dpdk.org \
/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).