From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: |WARNING| pw123053 [PATCH] event/cnxk: fix timer ops init in secondary
Date: Sun, 5 Feb 2023 07:34:18 +0100 (CET) [thread overview]
Message-ID: <20230205063418.747B8121E50@dpdk.org> (raw)
In-Reply-To: <20230205063347.6469-1-pbhagavatula@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/123053
_coding style issues_
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#93: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:384:
+ struct cnxk_tim_ring *tim_ring;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#93: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:384:
+ struct cnxk_tim_ring *tim_ring;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#102: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:408:
+ tim_ring = ((struct rte_event_timer_adapter_data
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#105: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:411:
+ if (tim_ring != NULL && rte_eal_process_type() == RTE_PROC_SECONDARY)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#106: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:412:
+ cnxk_tim_set_fp_ops(tim_ring);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#106: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:412:
+ cnxk_tim_set_fp_ops(tim_ring);
total: 0 errors, 6 warnings, 19 lines checked
next prev parent reply other threads:[~2023-02-05 6:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230205063347.6469-1-pbhagavatula@marvell.com>
2023-02-05 6:23 ` |SUCCESS| " qemudev
2023-02-05 6:27 ` qemudev
2023-02-05 6:34 ` checkpatch [this message]
2023-02-05 7:39 ` 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=20230205063418.747B8121E50@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).