From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Subject: |WARNING| pw124568 [RFC 2/2] eal: add high-performance timer facility
Date: Tue, 28 Feb 2023 10:47:11 +0100 (CET) [thread overview]
Message-ID: <20230228094711.D893F120D89@dpdk.org> (raw)
In-Reply-To: <20230228093916.87206-3-mattias.ronnblom@ericsson.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/124568
_coding style issues_
WARNING:TYPO_SPELLING: 'hierachical' may be misspelled - perhaps 'hierarchical'?
#125:
The htimer library employs per-lcore hierachical timer wheels and a
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#576: FILE: app/test/test_htimer_mgr.c:367:
+ bool *failure_occured;
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#583: FILE: app/test/test_htimer_mgr.c:374:
+ bool *failure_occured)
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#595: FILE: app/test/test_htimer_mgr.c:386:
+ timer->failure_occured = failure_occured;
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#595: FILE: app/test/test_htimer_mgr.c:386:
+ timer->failure_occured = failure_occured;
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#625: FILE: app/test/test_htimer_mgr.c:416:
+ *(test_timer->failure_occured) = true;
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#648: FILE: app/test/test_htimer_mgr.c:439:
+ bool *failure_occured;
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#655: FILE: app/test/test_htimer_mgr.c:446:
+ bool *failure_occured)
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#668: FILE: app/test/test_htimer_mgr.c:459:
+ timer->failure_occured = failure_occured;
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#668: FILE: app/test/test_htimer_mgr.c:459:
+ timer->failure_occured = failure_occured;
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#679: FILE: app/test/test_htimer_mgr.c:470:
+ bool *failure_occured = cancel_timer->failure_occured;
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#679: FILE: app/test/test_htimer_mgr.c:470:
+ bool *failure_occured = cancel_timer->failure_occured;
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#682: FILE: app/test/test_htimer_mgr.c:473:
+ *failure_occured = true;
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#695: FILE: app/test/test_htimer_mgr.c:486:
+ *failure_occured = true;
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#740: FILE: app/test/test_htimer_mgr.c:531:
+ bool failure_occured = false;
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#785: FILE: app/test/test_htimer_mgr.c:576:
+ &failure_occured);
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#813: FILE: app/test/test_htimer_mgr.c:604:
+ &failure_occured);
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#841: FILE: app/test/test_htimer_mgr.c:632:
+ if (failure_occured)
WARNING:TYPO_SPELLING: 'asyncronous' may be misspelled - perhaps 'asynchronous'?
#2902: FILE: lib/htimer/rte_htimer_mgr.h:399:
+ * Update HWT time and perform timer expiry and asyncronous operation
WARNING:TYPO_SPELLING: 'functino' may be misspelled - perhaps 'function'?
#2967: FILE: lib/htimer/rte_htimer_mgr.h:464:
+ * This functino returns the most recent time provided by this thread,
total: 0 errors, 20 warnings, 3391 lines checked
next parent reply other threads:[~2023-02-28 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230228093916.87206-3-mattias.ronnblom@ericsson.com>
2023-02-28 9:47 ` checkpatch [this message]
2023-03-01 8:18 ` |FAILURE| pw124569-124568 " qemudev
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=20230228094711.D893F120D89@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=mattias.ronnblom@ericsson.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).