From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Anatoly Burakov <anatoly.burakov@intel.com>
Subject: |WARNING| pw148977 [PATCH v1 1/1] usertools/devbind: update coding style
Date: Mon, 2 Dec 2024 16:11:09 +0100 (CET) [thread overview]
Message-ID: <20241202151109.E8A99124519@dpdk.org> (raw)
In-Reply-To: <3fb9cafaad635d583e20a02610c7c2c9cb7e2771.1733151400.git.anatoly.burakov@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/148977
_coding style issues_
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#500: FILE: usertools/dpdk-devbind.py:55:
+DEVICE_CAVIUM_TIM: DeviceMatchPattern = {
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#632: FILE: usertools/dpdk-devbind.py:187:
+ DEVICE_CAVIUM_TIM,
WARNING:TYPO_SPELLING: 'commmand' may be misspelled - perhaps 'command'?
#1328: FILE: usertools/dpdk-devbind.py:731:
+ """POD class to keep commmand-line arguments and context."""
total: 0 errors, 3 warnings, 1817 lines checked
next prev parent reply other threads:[~2024-12-02 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3fb9cafaad635d583e20a02610c7c2c9cb7e2771.1733151400.git.anatoly.burakov@intel.com>
2024-12-02 14:38 ` qemudev
2024-12-02 15:11 ` checkpatch [this message]
2024-12-02 15:22 ` |WARNING| pw148977 [PATCH] [v1, " 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=20241202151109.E8A99124519@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).