From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Henry Nadeau <hnadeau@iol.unh.edu>
Subject: |WARNING| pw104253 [PATCH] devtools: spell check
Date: Fri, 12 Nov 2021 18:03:26 +0100 (CET) [thread overview]
Message-ID: <20211112170326.EF610120735@dpdk.org> (raw)
In-Reply-To: <20211112170127.112401-1-hnadeau@iol.unh.edu>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/104253
_coding style issues_
ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit fatal: bad o ("f5cd3ed72b94505a7")'
#74:
[ upstream commit d4fb4eb08725a3e667042c1f5cd3ed72b94505a7 ]
WARNING:TYPO_SPELLING: 'exeptions' may be misspelled - perhaps 'exceptions'?
#79:
for word exeptions, and the regex file will exclude any regex patterns
WARNING:LONG_LINE_COMMENT: line length of 110 exceeds 100 columns
#123: FILE: devtools/spell_check.sh:26:
+ echo "-b Specify a different branch to be checked for changes against."
WARNING:LONG_LINE_COMMENT: line length of 101 exceeds 100 columns
#124: FILE: devtools/spell_check.sh:27:
+ echo "-d Specify a different dictionary to be used by aspell."
WARNING:LONG_LINE_COMMENT: line length of 108 exceeds 100 columns
#222: FILE: devtools/spell_check.sh:125:
+# Checking if separate dictionary was supplied, if not defaults to spell_check_dictionary.txt in current dir
WARNING:LONG_LINE_COMMENT: line length of 125 exceeds 100 columns
#234: FILE: devtools/spell_check.sh:137:
+ aspell --lang=en --encoding=utf-8 --ignore-case --ignore-repl pipe list -d en --ignore=3 --personal="$dictionary" |
WARNING:LONG_LINE: line length of 109 exceeds 100 columns
#269: FILE: devtools/spell_check.sh:172:
+ # run the spellcheck function over each file in parallel, appending misspellings to the output file
WARNING:LONG_LINE: line length of 110 exceeds 100 columns
#270: FILE: devtools/spell_check.sh:173:
+ parallel -j "$(nproc)" spellcheck_file {} "$allowed_words" "$dpdk_dir" "$regex_pattern" >> "$output"
WARNING:LONG_LINE: line length of 134 exceeds 100 columns
#272: FILE: devtools/spell_check.sh:175:
+ find . -name "*.rst" -type f | parallel -j "$(nproc)" spellcheck_file {} "$allowed_words" "$dpdk_dir" "$regex_pattern" >>"$output"
ERROR:TRAILING_WHITESPACE: trailing whitespace
#293: FILE: devtools/spell_check_dictionary.txt:1:
+personal_ws-1.1 en 2156 $
WARNING:TYPO_SPELLING: 'dettach' may be misspelled - perhaps 'detach'?
#1168: FILE: devtools/spell_check_dictionary.txt:876:
+dettach
WARNING:TYPO_SPELLING: 'dont' may be misspelled - perhaps 'don't'?
#1201: FILE: devtools/spell_check_dictionary.txt:909:
+dont
WARNING:TYPO_SPELLING: 'frequences' may be misspelled - perhaps 'frequencies'?
#1342: FILE: devtools/spell_check_dictionary.txt:1050:
+frequences
WARNING:TYPO_SPELLING: 'preemptable' may be misspelled - perhaps 'preemptible'?
#1905: FILE: devtools/spell_check_dictionary.txt:1613:
+preemptable
total: 2 errors, 12 warnings, 2348 lines checked
next parent reply other threads:[~2021-11-12 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211112170127.112401-1-hnadeau@iol.unh.edu>
2021-11-12 17:03 ` checkpatch [this message]
2021-11-12 17:38 ` |SUCCESS| " 0-day Robot
2021-11-12 17:31 |WARNING| " 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=20211112170326.EF610120735@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=hnadeau@iol.unh.edu \
--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).