From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Pravin Pathak <pravin.pathak@intel.com>
Subject: |WARNING| pw155018 [PATCH v1] event/dlb2: add support for stop and restart dlb device
Date: Sat, 5 Jul 2025 20:41:08 +0200 (CEST) [thread overview]
Message-ID: <20250705184108.29541125304@dpdk.org> (raw)
In-Reply-To: <20250705184209.924922-1-pravin.pathak@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/155018
_coding style issues_
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#119: FILE: drivers/event/dlb2/dlb2.c:1047:
+ dlb2->ev_ports[i].qm_port.hist_list = 0;
WARNING:TYPO_SPELLING: 'stoped' may be misspelled - perhaps 'stopped'?
#507: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:6264:
+ * traffic through it. Once a domain is stoped, its resources can no longer be
WARNING:TYPO_SPELLING: 'stoped' may be misspelled - perhaps 'stopped'?
#518: FILE: drivers/event/dlb2/pf/base/dlb2_resource.c:6275:
+ * EINVAL - the domain is not configured, or the domain is already stoped.
total: 0 errors, 3 warnings, 1133 lines checked
next prev parent reply other threads:[~2025-07-05 18:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250705184209.924922-1-pravin.pathak@intel.com>
2025-07-05 18:37 ` |SUCCESS| " qemudev
2025-07-05 18:41 ` checkpatch [this message]
2025-07-05 18:42 ` qemudev
2025-07-05 20:03 ` 0-day Robot
2025-07-05 20:12 ` |SUCCESS| pw155018 [PATCH] [v1] event/dlb2: add support for stop and dpdklab
2025-07-05 20:15 ` |PENDING| " dpdklab
2025-07-05 20:19 ` |SUCCESS| " dpdklab
2025-07-05 20:20 ` |PENDING| " dpdklab
2025-07-05 20:32 ` dpdklab
2025-07-05 20:45 ` |SUCCESS| " dpdklab
2025-07-05 20:49 ` dpdklab
2025-07-05 20:56 ` dpdklab
2025-07-05 20:57 ` |FAILURE| " dpdklab
2025-07-05 21:11 ` dpdklab
2025-07-05 21:17 ` |SUCCESS| " dpdklab
2025-07-05 21:22 ` |WARNING| " dpdklab
2025-07-05 21:50 ` |SUCCESS| " dpdklab
2025-07-05 21:58 ` |WARNING| " dpdklab
2025-07-05 22:02 ` |SUCCESS| " 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=20250705184108.29541125304@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=pravin.pathak@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).