From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Tirthendu Sarkar <tirthendu.sarkar@intel.com>
Subject: |WARNING| pw154497 [PATCH] event/dlb2: add datapath support in secondary processes
Date: Tue, 17 Jun 2025 06:56:38 +0200 (CEST) [thread overview]
Message-ID: <20250617045638.B562C1252C7@dpdk.org> (raw)
In-Reply-To: <20250617045607.245070-1-tirthendu.sarkar@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/154497
_coding style issues_
WARNING:TYPO_SPELLING: 'mmaped' may be misspelled - perhaps 'mapped'?
#96: FILE: drivers/event/dlb2/dlb2.c:3260:
+ if (!port_data->mmaped)
WARNING:TYPO_SPELLING: 'mmaped' may be misspelled - perhaps 'mapped'?
#107: FILE: drivers/event/dlb2/dlb2.c:3397:
+ if (!port_data->mmaped)
WARNING:TYPO_SPELLING: 'mmaped' may be misspelled - perhaps 'mapped'?
#125: FILE: drivers/event/dlb2/dlb2.c:4466:
+ if (!port_data->mmaped)
WARNING:TYPO_SPELLING: 'mmaped' may be misspelled - perhaps 'mapped'?
#143: FILE: drivers/event/dlb2/dlb2.c:4519:
+ if (!port_data->mmaped)
WARNING:TYPO_SPELLING: 'mmaped' may be misspelled - perhaps 'mapped'?
#243: FILE: drivers/event/dlb2/pf/dlb2_pf.c:58:
+ dlb2_port[i][DLB2_DIR_PORT].mmaped = false;
WARNING:TYPO_SPELLING: 'mmaped' may be misspelled - perhaps 'mapped'?
#248: FILE: drivers/event/dlb2/pf/dlb2_pf.c:63:
+ dlb2_port[i][DLB2_LDB_PORT].mmaped = false;
WARNING:TYPO_SPELLING: 'mmaped' may be misspelled - perhaps 'mapped'?
#259: FILE: drivers/event/dlb2/pf/dlb2_pf.c:74:
+ dlb2_port[i][DLB2_LDB_PORT].mmaped = true;
WARNING:TYPO_SPELLING: 'mmaped' may be misspelled - perhaps 'mapped'?
#264: FILE: drivers/event/dlb2/pf/dlb2_pf.c:79:
+ dlb2_port[i][DLB2_DIR_PORT].mmaped = true;
WARNING:TYPO_SPELLING: 'mmaped' may be misspelled - perhaps 'mapped'?
#281: FILE: drivers/event/dlb2/pf/dlb2_pf.c:378:
+ dlb2_port[response.id][DLB2_LDB_PORT].mmaped = true;
WARNING:TYPO_SPELLING: 'mmaped' may be misspelled - perhaps 'mapped'?
#309: FILE: drivers/event/dlb2/pf/dlb2_pf.c:461:
+ dlb2_port[response.id][DLB2_DIR_PORT].mmaped = true;
total: 0 errors, 10 warnings, 200 lines checked
next prev parent reply other threads:[~2025-06-17 4:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250617045607.245070-1-tirthendu.sarkar@intel.com>
2025-06-17 4:21 ` |SUCCESS| " qemudev
2025-06-17 4:25 ` qemudev
2025-06-17 4:56 ` checkpatch [this message]
2025-06-17 5:55 ` 0-day Robot
2025-06-17 5:59 ` |SUCCESS| pw154497 [PATCH] event/dlb2: add datapath support in secon dpdklab
2025-06-17 6:10 ` |PENDING| " dpdklab
2025-06-17 6:12 ` |SUCCESS| " dpdklab
2025-06-17 6:15 ` dpdklab
2025-06-17 6:21 ` dpdklab
2025-06-17 6:23 ` |FAILURE| " dpdklab
2025-06-17 6:26 ` dpdklab
2025-06-17 7:30 ` |PENDING| " dpdklab
2025-06-17 8:09 ` |SUCCESS| " dpdklab
2025-06-17 8:15 ` dpdklab
2025-06-17 8:41 ` dpdklab
2025-06-17 9:00 ` dpdklab
2025-06-17 9:01 ` dpdklab
2025-06-17 9:26 ` dpdklab
2025-06-17 9:57 ` |PENDING| " dpdklab
2025-06-17 10:13 ` |FAILURE| " dpdklab
2025-06-17 10:13 ` dpdklab
2025-06-17 10:14 ` dpdklab
2025-06-17 10:14 ` dpdklab
2025-06-17 10:14 ` dpdklab
2025-06-17 10:15 ` dpdklab
2025-06-17 10:16 ` dpdklab
2025-06-17 12:11 ` |SUCCESS| " dpdklab
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=20250617045638.B562C1252C7@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=tirthendu.sarkar@intel.com \
/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).