From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Anatoly Burakov <anatoly.burakov@intel.com>
Subject: |WARNING| pw153383 [PATCH v9 1/3] cmdline: use C standard library as number parser
Date: Fri, 9 May 2025 15:40:59 +0200 (CEST) [thread overview]
Message-ID: <20250509134059.56C35123FBC@dpdk.org> (raw)
In-Reply-To: <9ea91fbec73396343179143e9c3b058148f05c5b.1746797960.git.anatoly.burakov@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/153383
_coding style issues_
ERROR:ELSE_AFTER_BRACE: else should follow close brace '}'
#373: FILE: lib/cmdline/cmdline_parse_num.c:182:
+ }
+ else {
WARNING:BRACES: braces {} are not necessary for any arm of this statement
#384: FILE: lib/cmdline/cmdline_parse_num.c:188:
+ if (c == '0') {
[...]
- else {
[...]
ERROR:ELSE_AFTER_BRACE: else should follow close brace '}'
#388: FILE: lib/cmdline/cmdline_parse_num.c:191:
}
+ else {
WARNING:BRACES: braces {} are not necessary for single statement blocks
#388: FILE: lib/cmdline/cmdline_parse_num.c:191:
+ else {
st = ERROR;
}
WARNING:BRACES: braces {} are not necessary for any arm of this statement
#398: FILE: lib/cmdline/cmdline_parse_num.c:197:
+ if (c == 'b') {
[...]
- else if (c >= '0' && c <= '7') {
[...]
WARNING:TYPO_SPELLING: 'ressize' may be misspelled - perhaps 'resize'?
#605: FILE: lib/cmdline/cmdline_parse_num.c:282:
+ unsigned ressize)
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#605: FILE: lib/cmdline/cmdline_parse_num.c:282:
+ unsigned ressize)
WARNING:TYPO_SPELLING: 'ressize' may be misspelled - perhaps 'resize'?
#618: FILE: lib/cmdline/cmdline_parse_num.c:295:
+ if (res && check_res_size(&nd, ressize) < 0)
total: 2 errors, 6 warnings, 532 lines checked
parent reply other threads:[~2025-05-09 13:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <9ea91fbec73396343179143e9c3b058148f05c5b.1746797960.git.anatoly.burakov@intel.com>]
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=20250509134059.56C35123FBC@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=anatoly.burakov@intel.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).