From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Harry van Haaren <harry.van.haaren@intel.com>
Subject: |WARNING| pw130999 [PATCH 2/2] event/sw: fix ordering corruption with op release
Date: Thu, 31 Aug 2023 18:48:18 +0200 (CEST) [thread overview]
Message-ID: <20230831164818.9588B121090@dpdk.org> (raw)
In-Reply-To: <20230831164736.2472671-2-harry.van.haaren@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/130999
_coding style issues_
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#105: FILE: drivers/event/sw/sw_evdev_scheduler.c:394:
+ struct sw_hist_list_entry *hist_entry;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#105: FILE: drivers/event/sw/sw_evdev_scheduler.c:394:
+ struct sw_hist_list_entry *hist_entry;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#113: FILE: drivers/event/sw/sw_evdev_scheduler.c:405:
+ /* Assign current hist-list entry to the rob_entry, to
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#116: FILE: drivers/event/sw/sw_evdev_scheduler.c:408:
+ rob_ptr = hist_entry->rob_entry;
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#119: FILE: drivers/event/sw/sw_evdev_scheduler.c:411:
+ * RELEASE events must clear hist-list, but MIGHT NOT
WARNING:TYPO_SPELLING: 'hist' may be misspelled - perhaps 'heist'?
#122: FILE: drivers/event/sw/sw_evdev_scheduler.c:414:
+ hist_entry->rob_entry = NULL;
total: 0 errors, 6 warnings, 82 lines checked
next prev parent reply other threads:[~2023-08-31 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230831164736.2472671-2-harry.van.haaren@intel.com>
2023-08-31 16:36 ` |SUCCESS| pw131000-130999 " qemudev
2023-08-31 16:40 ` qemudev
2023-08-31 16:48 ` checkpatch [this message]
2023-08-31 17:39 ` |SUCCESS| pw130999 " 0-day Robot
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=20230831164818.9588B121090@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).