From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Rakesh Kudurumalla <rkudurumalla@marvell.com>
Subject: |WARNING| pw134869 [PATCH 2/2] net/cnxk: dump Rx descriptor info to file
Date: Tue, 5 Dec 2023 10:46:32 +0100 (CET) [thread overview]
Message-ID: <20231205094632.40DBA121E42@dpdk.org> (raw)
In-Reply-To: <20231205094539.1377142-2-rkudurumalla@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/134869
_coding style issues_
WARNING:TYPO_SPELLING: 'availble' may be misspelled - perhaps 'available'?
#130: FILE: drivers/net/cnxk/cn10k_ethdev.c:694:
+ int availble_pkts;
WARNING:TYPO_SPELLING: 'availble' may be misspelled - perhaps 'available'?
#133: FILE: drivers/net/cnxk/cn10k_ethdev.c:697:
+ availble_pkts = cn10k_nix_rx_avail_get(rxq);
WARNING:TYPO_SPELLING: 'availble' may be misspelled - perhaps 'available'?
#135: FILE: drivers/net/cnxk/cn10k_ethdev.c:699:
+ if ((offset + num - 1) >= availble_pkts) {
WARNING:TYPO_SPELLING: 'availble' may be misspelled - perhaps 'available'?
#213: FILE: drivers/net/cnxk/cn9k_ethdev.c:700:
+ int availble_pkts;
WARNING:TYPO_SPELLING: 'availble' may be misspelled - perhaps 'available'?
#215: FILE: drivers/net/cnxk/cn9k_ethdev.c:702:
+ availble_pkts = cn9k_nix_rx_avail_get(rxq);
WARNING:TYPO_SPELLING: 'availble' may be misspelled - perhaps 'available'?
#217: FILE: drivers/net/cnxk/cn9k_ethdev.c:704:
+ if ((offset + num - 1) >= availble_pkts) {
total: 0 errors, 6 warnings, 0 checks, 144 lines checked
next parent reply other threads:[~2023-12-05 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231205094539.1377142-2-rkudurumalla@marvell.com>
2023-12-05 9:46 ` checkpatch [this message]
2023-12-05 10:45 ` |SUCCESS| " 0-day Robot
2023-12-06 2:47 ` |SUCCESS| pw134867-134869 " qemudev
2023-12-06 2:52 ` qemudev
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=20231205094632.40DBA121E42@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=rkudurumalla@marvell.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).