From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Harry van Haaren <harry.van.haaren@intel.com>
Subject: |WARNING| pw131000 [PATCH 1/2] event/sw: add selftest for ordered history list
Date: Thu, 31 Aug 2023 18:48:21 +0200 (CEST) [thread overview]
Message-ID: <20230831164821.828221210A9@dpdk.org> (raw)
In-Reply-To: <20230831164736.2472671-1-harry.van.haaren@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/131000
_coding style issues_
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#73:
iterating HIST_LIST times afterwards.
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#89: FILE: drivers/event/sw/sw_evdev_selftest.c:2963:
+ordered_atomic_hist_completion(struct test *t)
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#120: FILE: drivers/event/sw/sw_evdev_selftest.c:2994:
+ * CPU, which may cause hist-list corruption (by not comleting)
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#147: FILE: drivers/event/sw/sw_evdev_selftest.c:3021:
+ * but might not be if the hist-list bug exists. Call scheduler to make
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#153: FILE: drivers/event/sw/sw_evdev_selftest.c:3027:
+ /* Enqueue 1x atomic event, to then FORWARD to trigger atomic hist-list
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#175: FILE: drivers/event/sw/sw_evdev_selftest.c:3049:
+ /* Deq ATM event, then forward it for more than HIST_LIST_SIZE times,
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#178: FILE: drivers/event/sw/sw_evdev_selftest.c:3052:
+ for (int i = 0; i < SW_PORT_HIST_LIST + 2; i++) {
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#180: FILE: drivers/event/sw/sw_evdev_selftest.c:3054:
+ printf("%d: failed to dequeue, did corrupt ORD hist "
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#185: FILE: drivers/event/sw/sw_evdev_selftest.c:3059:
+ /* Re-enqueue the ATM event as FWD, trigger hist-list. */
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#196: FILE: drivers/event/sw/sw_evdev_selftest.c:3070:
+ /* If HIST-LIST + N count of dequeues succeed above, the hist list
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#196: FILE: drivers/event/sw/sw_evdev_selftest.c:3070:
+ /* If HIST-LIST + N count of dequeues succeed above, the hist list
WARNING:TYPO_SPELLING: 'HIST' may be misspelled - perhaps 'HEIST'?
#201: FILE: drivers/event/sw/sw_evdev_selftest.c:3075:
+ /* release the ATM event that's been forwarded HIST_LIST times */
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#221: FILE: drivers/event/sw/sw_evdev_selftest.c:3517:
+ printf("*** Running Ordered & Atomic hist-list completion test...
");
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#222: FILE: drivers/event/sw/sw_evdev_selftest.c:3518:
+ ret = ordered_atomic_hist_completion(t);
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#224: FILE: drivers/event/sw/sw_evdev_selftest.c:3520:
+ printf("ERROR - Ordered & Atomic hist-list test FAILED.
");
total: 0 errors, 15 warnings, 144 lines checked
parent reply other threads:[~2023-08-31 16:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230831164736.2472671-1-harry.van.haaren@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=20230831164821.828221210A9@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=harry.van.haaren@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).