From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw92211 [PATCH v2 25/33] event/cnxk: add timer adapter info function
Date: Mon, 26 Apr 2021 19:49:28 +0200 (CEST) [thread overview]
Message-ID: <20210426174928.CFE70121158@dpdk.org> (raw)
In-Reply-To: <20210426174441.2302-26-pbhagavatula@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/92211
_coding style issues_
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#80:
Add TIM event timer adapter info get function.
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#97: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:80:
+cnxk_tim_ring_info_get(const struct rte_event_timer_adapter *adptr,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#100: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:83:
+ struct cnxk_tim_ring *tim_ring = adptr->data->adapter_priv;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#100: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:83:
+ struct cnxk_tim_ring *tim_ring = adptr->data->adapter_priv;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#102: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:85:
+ adptr_info->max_tmo_ns = tim_ring->max_tout;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#103: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:86:
+ adptr_info->min_resolution_ns = tim_ring->tck_nsec;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#115: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:233:
+ cnxk_tim_ops.get_info = cnxk_tim_ring_info_get;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#115: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:233:
+ cnxk_tim_ops.get_info = cnxk_tim_ring_info_get;
total: 0 errors, 8 warnings, 25 lines checked
parent reply other threads:[~2021-04-26 17:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210426174441.2302-26-pbhagavatula@marvell.com>]
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=20210426174928.CFE70121158@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).