From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andre Muezerie <andremue@linux.microsoft.com>
Subject: |WARNING| pw150203 [PATCH] drivers/net: fix indication of allocation
Date: Fri, 17 Jan 2025 21:51:02 +0100 (CET) [thread overview]
Message-ID: <20250117205102.564B8126FEB@dpdk.org> (raw)
In-Reply-To: <1737147093-11172-1-git-send-email-andremue@linux.microsoft.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/150203
_coding style issues_
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#81: FILE: drivers/net/bnxt/tf_core/tf_sram_mgr.c:952:
+ *parms->is_allocated = false;
WARNING:TYPO_SPELLING: 'parms' may be misspelled - perhaps 'params'?
#90: FILE: drivers/net/bnxt/tf_core/tf_sram_mgr.c:967:
+ *parms->is_allocated = false;
total: 0 errors, 2 warnings, 0 checks, 16 lines checked
next prev parent reply other threads:[~2025-01-17 20:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1737147093-11172-1-git-send-email-andremue@linux.microsoft.com>
2025-01-17 20:21 ` |SUCCESS| " qemudev
2025-01-17 20:25 ` qemudev
2025-01-17 20:51 ` checkpatch [this message]
2025-01-17 22:04 ` 0-day Robot
2025-01-17 22:15 ` dpdklab
2025-01-17 22:25 ` dpdklab
2025-01-17 22:26 ` dpdklab
2025-01-17 22:30 ` |PENDING| " dpdklab
2025-01-17 22:31 ` dpdklab
2025-01-17 22:34 ` |SUCCESS| " dpdklab
2025-01-17 22:38 ` dpdklab
2025-01-17 22:39 ` dpdklab
2025-01-17 22:39 ` dpdklab
2025-01-17 22:45 ` dpdklab
2025-01-17 22:48 ` |PENDING| " dpdklab
2025-01-17 22:52 ` |SUCCESS| " dpdklab
2025-01-17 22:54 ` dpdklab
2025-01-17 23:13 ` dpdklab
2025-01-17 23:21 ` |WARNING| " dpdklab
2025-01-17 23:21 ` dpdklab
2025-01-17 23:26 ` |SUCCESS| " dpdklab
2025-01-17 23:36 ` |WARNING| " dpdklab
2025-01-17 23:37 ` |SUCCESS| " dpdklab
2025-01-17 23:38 ` |WARNING| " dpdklab
2025-01-17 23:42 ` |SUCCESS| " dpdklab
2025-01-18 0:18 ` 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=20250117205102.564B8126FEB@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=andremue@linux.microsoft.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).