From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Haifei Luo <haifeil@nvidia.com>
Subject: |WARNING| pw137200 [PATCH] net/mlx5: link status change for bonding cases
Date: Mon, 26 Feb 2024 13:04:35 +0100 (CET) [thread overview]
Message-ID: <20240226120435.23536122320@dpdk.org> (raw)
In-Reply-To: <20240226120341.175710-1-haifeil@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/137200
_coding style issues_
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#122:
master and slave interface netlink events indicate the bonding link
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#122:
master and slave interface netlink events indicate the bonding link
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#124:
bonding's master/slave.
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#124:
bonding's master/slave.
WARNING:TYPO_SPELLING: 'master' may be misspelled - perhaps 'primary'?
#128:
and it should compare the link status of the bonding master to detect
WARNING:TYPO_SPELLING: 'IFF' may be misspelled - perhaps 'IF'?
#182: FILE: drivers/net/mlx5/linux/mlx5_ethdev_os.c:809:
+ ((ifr.ifr_flags & IFF_UP) && (ifr.ifr_flags & IFF_RUNNING));
WARNING:TYPO_SPELLING: 'IFF' may be misspelled - perhaps 'IF'?
#182: FILE: drivers/net/mlx5/linux/mlx5_ethdev_os.c:809:
+ ((ifr.ifr_flags & IFF_UP) && (ifr.ifr_flags & IFF_RUNNING));
total: 0 errors, 7 warnings, 0 checks, 72 lines checked
next prev parent reply other threads:[~2024-02-26 12:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240226120341.175710-1-haifeil@nvidia.com>
2024-02-26 11:41 ` |SUCCESS| " qemudev
2024-02-26 11:46 ` qemudev
2024-02-26 12:04 ` checkpatch [this message]
2024-02-26 13:04 ` 0-day Robot
2024-02-28 2:23 ` |SUCCESS| pw137200 [PATCH] net/mlx5: link status change for bonding dpdklab
2024-02-28 2:26 ` dpdklab
2024-02-28 2:29 ` dpdklab
2024-02-28 2:31 ` 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=20240226120435.23536122320@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=haifeil@nvidia.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).