From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw144131 [PATCH v2] devtools: fix false positive from checkpatch
Date: Tue, 17 Sep 2024 18:57:26 +0200 (CEST) [thread overview]
Message-ID: <20240917165726.0BA04121D10@dpdk.org> (raw)
In-Reply-To: <20240917165611.9943-1-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/144131
_coding style issues_
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#85:
The codespell dictionary has "stdio" in its bad word list,
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#86:
but stdio.h is often used in DPDK code and creates bogus false
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#117: FILE: devtools/build-dict.sh:24:
+sed '/^stdio->/d' |
total: 0 errors, 3 warnings, 17 lines checked
next prev parent reply other threads:[~2024-09-17 16:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240917165611.9943-1-stephen@networkplumber.org>
2024-09-17 16:29 ` |SUCCESS| " qemudev
2024-09-17 16:33 ` qemudev
2024-09-17 16:57 ` checkpatch [this message]
2024-09-17 17:44 ` 0-day Robot
2024-09-17 22:02 ` |SUCCESS| pw144131 [PATCH] [v2] devtools: fix false positive from ch dpdklab
2024-09-18 0:03 ` dpdklab
2024-09-18 0:04 ` dpdklab
2024-09-18 0:27 ` dpdklab
2024-09-18 0:40 ` dpdklab
2024-09-18 2:05 ` |PENDING| " dpdklab
2024-09-18 2:22 ` |SUCCESS| " dpdklab
2024-09-18 2:31 ` |PENDING| " dpdklab
2024-09-18 3:18 ` |SUCCESS| " dpdklab
2024-09-18 3:26 ` |PENDING| " dpdklab
2024-09-18 4:13 ` |SUCCESS| " dpdklab
2024-09-18 4:14 ` dpdklab
2024-09-18 4:50 ` dpdklab
2024-09-18 5:06 ` dpdklab
2024-09-18 5:07 ` dpdklab
2024-09-18 5:09 ` dpdklab
2024-09-18 6:08 ` dpdklab
2024-09-18 10:24 ` dpdklab
2024-09-18 12:35 ` dpdklab
2024-09-22 9:52 ` dpdklab
2024-09-22 10:05 ` 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=20240917165726.0BA04121D10@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).