From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-test-report] |WARNING| pw88430 [PATCH v2] pflock: implementation of phase-fair reader writer locks
Date: Wed, 3 Mar 2021 19:31:43 +0100 (CET) [thread overview]
Message-ID: <20210303183143.3DBA03F9@dpdk.org> (raw)
In-Reply-To: <20210303183019.70700-1-sthemmin@microsoft.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/88430
_coding style issues_
WARNING:TYPO_SPELLING: 'reverese' may be misspelled - perhaps 'reverse'?
#432: FILE: app/test/test_pflock.c:281:
+ /* update by bytes in reverese order */
WARNING:TYPO_SPELLING: 'reverese' may be misspelled - perhaps 'reverse'?
#449: FILE: app/test/test_pflock.c:298:
+ /* restore by bytes in reverese order */
WARNING:TYPO_SPELLING: 'avaialble' may be misspelled - perhaps 'available'?
#641: FILE: app/test/test_pflock.c:490:
+ /* start read test on all avaialble lcores */
WARNING:TYPO_SPELLING: 'PRES' may be misspelled - perhaps 'PRESS'?
#796: FILE: lib/librte_eal/include/generic/rte_pflock.h:61:
+#define RTE_PFLOCK_PRES 0x2 /* Writer present bit. */
WARNING:TYPO_SPELLING: 'PRES' may be misspelled - perhaps 'PRESS'?
#930: FILE: lib/librte_eal/include/generic/rte_pflock.h:195:
+ (ticket & RTE_PFLOCK_PHID) | RTE_PFLOCK_PRES,
WARNING:TYPO_SPELLING: 'PRES' may be misspelled - perhaps 'PRESS'?
#996: FILE: lib/librte_eal/include/generic/rte_pflock.h:261:
+ (ticket & RTE_PFLOCK_PHID) | RTE_PFLOCK_PRES,
total: 0 errors, 6 warnings, 906 lines checked
next parent reply other threads:[~2021-03-03 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210303183019.70700-1-sthemmin@microsoft.com>
2021-03-03 18:31 ` checkpatch [this message]
2021-03-03 19:56 ` [dpdk-test-report] |SUCCESS| pw88430 " 0-day Robot
2021-03-03 19:57 ` [dpdk-test-report] |SUCCESS| pw88430 [dpdk-dev] [PATCH v2] " 0-day Robot
2021-03-03 20:57 ` 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=20210303183143.3DBA03F9@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=stephen@networkplumber.org \
--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).