From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw89670 [PATCH v3 4/4] event/octeontx2: timer always use virtual counter
Date: Tue, 23 Mar 2021 09:45:44 +0100 (CET) [thread overview]
Message-ID: <20210323084544.19C5A2901@dpdk.org> (raw)
In-Reply-To: <20210323084439.3898-4-pbhagavatula@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/89670
_coding style issues_
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#104: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:357:
+ bkt_cyc = tim_cntvct();
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#126: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:393:
+ tim_ring->tck_int = NSEC2TICK(tim_ring->tck_nsec, tim_cntfrq());
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#126: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:393:
+ tim_ring->tck_int = NSEC2TICK(tim_ring->tck_nsec, tim_cntfrq());
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#126: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:393:
+ tim_ring->tck_int = NSEC2TICK(tim_ring->tck_nsec, tim_cntfrq());
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#136: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:461:
+ uint64_t bkt_cyc = tim_cntvct() - tim_ring->ring_start_cyc;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#136: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:461:
+ uint64_t bkt_cyc = tim_cntvct() - tim_ring->ring_start_cyc;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#150: FILE: drivers/event/octeontx2/otx2_tim_evdev.h:181:
+tim_cntvct(void)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#156: FILE: drivers/event/octeontx2/otx2_tim_evdev.h:187:
+tim_cntfrq(void)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#162: FILE: drivers/event/octeontx2/otx2_tim_evdev.h:193:
+tim_cntvct(void)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#168: FILE: drivers/event/octeontx2/otx2_tim_evdev.h:199:
+tim_cntfrq(void)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#186: FILE: drivers/event/octeontx2/otx2_tim_worker.c:44:
+ uint64_t cur_cyc = tim_cntvct();
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#192: FILE: drivers/event/octeontx2/otx2_tim_worker.c:49:
+ cur_cyc = tim_cntvct();
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#205: FILE: drivers/event/octeontx2/otx2_tim_worker.h:135:
+ const uint64_t bkt_cyc = tim_cntvct() - tim_ring->ring_start_cyc;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#205: FILE: drivers/event/octeontx2/otx2_tim_worker.h:135:
+ const uint64_t bkt_cyc = tim_cntvct() - tim_ring->ring_start_cyc;
total: 0 errors, 14 warnings, 92 lines checked
next parent reply other threads:[~2021-03-23 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210323084439.3898-4-pbhagavatula@marvell.com>
2021-03-23 8:45 ` checkpatch [this message]
2021-03-23 9:57 ` [dpdk-test-report] |SUCCESS| pw89670 [dpdk-dev] " 0-day Robot
2021-03-23 15:55 ` [dpdk-test-report] |WARNING| pw89670 " 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=20210323084544.19C5A2901@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=pbhagavatula@marvell.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).