automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw88223 [PATCH 4/4] event/octeontx2: timer always use virtual counter
Date: Thu, 25 Feb 2021 13:25:30 +0100 (CET)	[thread overview]
Message-ID: <20210225122530.8F19C2A6C@dpdk.org> (raw)
In-Reply-To: <20210225122315.6350-4-pbhagavatula@marvell.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/88223

_coding style issues_


WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#96: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:357:
+		bkt_cyc = tim_cntvct();

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#118: 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'?
#118: 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'?
#118: 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'?
#128: 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'?
#128: 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'?
#142: FILE: drivers/event/octeontx2/otx2_tim_evdev.h:181:
+tim_cntvct(void)

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#151: FILE: drivers/event/octeontx2/otx2_tim_evdev.h:190:
+tim_cntfrq(void)

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#160: FILE: drivers/event/octeontx2/otx2_tim_evdev.h:199:
+tim_cntvct(void)

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#166: FILE: drivers/event/octeontx2/otx2_tim_evdev.h:205:
+tim_cntfrq(void)

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#184: FILE: drivers/event/octeontx2/otx2_tim_worker.c:44:
+	uint64_t cur_cyc = tim_cntvct();

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#190: FILE: drivers/event/octeontx2/otx2_tim_worker.c:49:
+		cur_cyc = tim_cntvct();

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#203: 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'?
#203: 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, 98 lines checked

       reply	other threads:[~2021-02-25 12:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210225122315.6350-4-pbhagavatula@marvell.com>
2021-02-25 12:25 ` checkpatch [this message]
2021-02-25 13:55 ` [dpdk-test-report] |FAILURE| pw88223 " 0-day Robot
2021-02-25 13:56 ` [dpdk-test-report] |SUCCESS| pw88223 [dpdk-dev] [PATCH 4/4] " 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=20210225122530.8F19C2A6C@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).