From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw159480 [PATCH 5/7] net/bnxt: fix uninitialized warning
Date: Sun, 28 Dec 2025 19:46:02 +0100 (CET) [thread overview]
Message-ID: <20251228184602.CE7C5124270@dpdk.org> (raw)
In-Reply-To: <20251228184300.541639-6-stephen@networkplumber.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/159480
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#107:
inlined from ‘ulp_blob_push’ at ../drivers/net/bnxt/tf_ulp/ulp_utils.h:407:8,
WARNING:TYPO_SPELLING: 'clen' may be misspelled - perhaps 'clean'?
#136: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2449:
+ if (clen > 32) {
^^^^
WARNING:TYPO_SPELLING: 'clen' may be misspelled - perhaps 'clean'?
#137: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper.c:2450:
+ BNXT_DRV_DBG(ERR, "Key size bits %d too large
", clen);
^^^^
WARNING:TYPO_SPELLING: 'clen' may be misspelled - perhaps 'clean'?
#152: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper_tfc.c:93:
+ if (clen > 32) {
^^^^
WARNING:TYPO_SPELLING: 'clen' may be misspelled - perhaps 'clean'?
#153: FILE: drivers/net/bnxt/tf_ulp/ulp_mapper_tfc.c:94:
+ BNXT_DRV_DBG(ERR, "Key size bits %d too large
", clen);
^^^^
total: 0 errors, 5 warnings, 0 checks, 21 lines checked
parent reply other threads:[~2025-12-28 18:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20251228184300.541639-6-stephen@networkplumber.org>]
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=20251228184602.CE7C5124270@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=stephen@networkplumber.org \
--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).