From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: madhuker.mythri@oracle.com
Subject: |WARNING| pw155001 [PATCH] net/bonding: avoid RSS reta update in flow-isolation mode
Date: Thu, 3 Jul 2025 13:37:41 +0200 (CEST) [thread overview]
Message-ID: <20250703113741.7E5EF125302@dpdk.org> (raw)
In-Reply-To: <20250703113736.6889-1-madhuker.mythri@oracle.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/155001
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#98:
In bonding PMD, member_start() function checks whether RSS(mq_mode) is enabled
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#124: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1908:
+ * bonding, synchronize RETA */
ERROR:TRAILING_WHITESPACE: trailing whitespace
#125: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1909:
+^Iif ((internals->flow_isolated_valid == 0) && $
CHECK:UNNECESSARY_PARENTHESES: Unnecessary parentheses around 'internals->flow_isolated_valid == 0'
#125: FILE: drivers/net/bonding/rte_eth_bond_pmd.c:1909:
+ if ((internals->flow_isolated_valid == 0) &&
+ (bonding_eth_dev->data->dev_conf.rxmode.mq_mode & RTE_ETH_MQ_RX_RSS)) {
total: 1 errors, 2 warnings, 1 checks, 16 lines checked
next prev parent reply other threads:[~2025-07-03 11:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250703113736.6889-1-madhuker.mythri@oracle.com>
2025-07-03 11:23 ` |SUCCESS| " qemudev
2025-07-03 11:28 ` qemudev
2025-07-03 11:37 ` checkpatch [this message]
2025-07-03 12:43 ` 0-day Robot
2025-07-03 16:17 ` |SUCCESS| pw155001 [PATCH] net/bonding: avoid RSS reta update in flo dpdklab
2025-07-03 16:25 ` dpdklab
2025-07-03 17:00 ` dpdklab
2025-07-03 17:13 ` |PENDING| " dpdklab
2025-07-03 17:14 ` dpdklab
2025-07-03 17:27 ` |SUCCESS| " 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=20250703113741.7E5EF125302@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=madhuker.mythri@oracle.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).