From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Shijith Thotton <sthotton@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw89349 [PATCH v3 3/3] event/octeontx2: add timer periodic mode support
Date: Wed, 17 Mar 2021 09:07:35 +0100 (CET) [thread overview]
Message-ID: <20210317080735.A308A6CA1@dpdk.org> (raw)
In-Reply-To: <51c875237a4f639dd566eca8cfc181aecc06b513.1615967694.git.sthotton@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/89349
_coding style issues_
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#95: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:68:
+ adptr_info->min_resolution_ns = tim_ring->ena_periodic ?
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#96: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:69:
+ tim_ring->max_tout : tim_ring->tck_nsec;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#96: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:69:
+ tim_ring->max_tout : tim_ring->tck_nsec;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#105: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:167:
+ tim_ring->ena_dfb = tim_ring->ena_periodic ? 1 : 0;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#105: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:167:
+ tim_ring->ena_dfb = tim_ring->ena_periodic ? 1 : 0;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#143: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:315:
+ tim_ring->max_tout = is_periodic ?
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#149: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:321:
+ tim_ring->ena_periodic = is_periodic;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#158: FILE: drivers/event/octeontx2/otx2_tim_evdev.c:369:
+ cfg_req->enableperiodic = tim_ring->ena_periodic;
total: 0 errors, 8 warnings, 82 lines checked
next parent reply other threads:[~2021-03-17 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51c875237a4f639dd566eca8cfc181aecc06b513.1615967694.git.sthotton@marvell.com>
2021-03-17 8:07 ` checkpatch [this message]
2021-03-17 9:55 ` [dpdk-test-report] |SUCCESS| pw89349 " 0-day Robot
2021-03-17 9:57 ` [dpdk-test-report] |SUCCESS| pw89349 [dpdk-dev] [PATCH v3 3/3] " 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=20210317080735.A308A6CA1@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=sthotton@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).