From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw74951 [PATCH] event/octeontx: validate events requested against available
Date: Tue, 28 Jul 2020 20:23:17 +0200 (CEST) [thread overview]
Message-ID: <20200728182317.E4C681BFDA@dpdk.org> (raw)
In-Reply-To: <20200728182224.1359-1-pbhagavatula@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/74951
_coding style issues_
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#78:
events configured across all the RX/TIM event adapters.
WARNING:LONG_LINE: line over 100 characters
#180: FILE: drivers/event/octeontx/ssovf_evdev.c:423:
+ "Max available events %"PRIu32" requested events in rxq pool %"PRIu32"",
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#287: FILE: drivers/event/octeontx/ssovf_evdev.h:153:
+ uint16_t tim_ring_cnt;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#288: FILE: drivers/event/octeontx/ssovf_evdev.h:154:
+ uint16_t *tim_ring_ids;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#325: FILE: drivers/event/octeontx/timvf_evdev.c:234:
+ uint8_t tim_ring_id;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#353: FILE: drivers/event/octeontx/timvf_evdev.c:274:
+ for (i = 0; i < edev->tim_ring_cnt; i++) {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#354: FILE: drivers/event/octeontx/timvf_evdev.c:275:
+ if (edev->tim_ring_ids[i] == UINT16_MAX)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#361: FILE: drivers/event/octeontx/timvf_evdev.c:282:
+ edev->tim_ring_cnt++;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#362: FILE: drivers/event/octeontx/timvf_evdev.c:283:
+ old_ptr = edev->tim_ring_ids;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#363: FILE: drivers/event/octeontx/timvf_evdev.c:284:
+ edev->tim_ring_ids =
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#364: FILE: drivers/event/octeontx/timvf_evdev.c:285:
+ rte_realloc(edev->tim_ring_ids,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#365: FILE: drivers/event/octeontx/timvf_evdev.c:286:
+ sizeof(uint16_t) * edev->tim_ring_cnt, 0);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#366: FILE: drivers/event/octeontx/timvf_evdev.c:287:
+ if (edev->tim_ring_ids == NULL) {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#367: FILE: drivers/event/octeontx/timvf_evdev.c:288:
+ edev->tim_ring_ids = old_ptr;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#368: FILE: drivers/event/octeontx/timvf_evdev.c:289:
+ edev->tim_ring_cnt--;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#374: FILE: drivers/event/octeontx/timvf_evdev.c:295:
+ edev->tim_ring_ids[free_idx] = tim_ring_id;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#374: FILE: drivers/event/octeontx/timvf_evdev.c:295:
+ edev->tim_ring_ids[free_idx] = tim_ring_id;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#390: FILE: drivers/event/octeontx/timvf_evdev.c:372:
+ for (i = 0; i < edev->tim_ring_cnt; i++) {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#391: FILE: drivers/event/octeontx/timvf_evdev.c:373:
+ if (edev->tim_ring_ids[i] == timr->tim_ring_id) {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#391: FILE: drivers/event/octeontx/timvf_evdev.c:373:
+ if (edev->tim_ring_ids[i] == timr->tim_ring_id) {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#393: FILE: drivers/event/octeontx/timvf_evdev.c:375:
+ edev->tim_ring_ids[i] = UINT16_MAX;
total: 0 errors, 21 warnings, 297 lines checked
next parent reply other threads:[~2020-07-28 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200728182224.1359-1-pbhagavatula@marvell.com>
2020-07-28 18:23 ` checkpatch [this message]
2020-07-28 19:59 ` [dpdk-test-report] |SUCCESS| pw74951 " 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=20200728182317.E4C681BFDA@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).