From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: vanshika.shukla@nxp.com
Subject: |WARNING| pw154911 [v5 8/9] bus/dpaa: improve DPAA cleanup
Date: Tue, 1 Jul 2025 13:37:43 +0200 (CEST) [thread overview]
Message-ID: <20250701113743.49B801252DA@dpdk.org> (raw)
In-Reply-To: <20250701113707.2793004-9-vanshika.shukla@nxp.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/154911
_coding style issues_
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#164: FILE: drivers/bus/dpaa/dpaa_bus.c:923:
+ unsigned int lcore_id;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#166: FILE: drivers/bus/dpaa/dpaa_bus.c:925:
+ if (!dpaa_bus_global_init)$
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (7, 15)
#166: FILE: drivers/bus/dpaa/dpaa_bus.c:925:
+ if (!dpaa_bus_global_init)
+ return;
ERROR:CODE_INDENT: code indent should use tabs where possible
#167: FILE: drivers/bus/dpaa/dpaa_bus.c:926:
+ return;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#167: FILE: drivers/bus/dpaa/dpaa_bus.c:926:
+ return;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#170: FILE: drivers/bus/dpaa/dpaa_bus.c:929:
+ RTE_LCORE_FOREACH_WORKER(lcore_id) {$
ERROR:CODE_INDENT: code indent should use tabs where possible
#171: FILE: drivers/bus/dpaa/dpaa_bus.c:930:
+ /* Check for non zero id */$
ERROR:CODE_INDENT: code indent should use tabs where possible
#172: FILE: drivers/bus/dpaa/dpaa_bus.c:931:
+ dpaa_portal_finish((void *)dpaa_portals[lcore_id]);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#172: FILE: drivers/bus/dpaa/dpaa_bus.c:931:
+ dpaa_portal_finish((void *)dpaa_portals[lcore_id]);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#173: FILE: drivers/bus/dpaa/dpaa_bus.c:932:
+ }$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#174: FILE: drivers/bus/dpaa/dpaa_bus.c:933:
+ dpaa_portal_finish((void *)DPAA_PER_LCORE_PORTAL);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#175: FILE: drivers/bus/dpaa/dpaa_bus.c:934:
+ dpaa_bus_global_init = 0;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#176: FILE: drivers/bus/dpaa/dpaa_bus.c:935:
+ DPAA_BUS_DEBUG("Worker thread clean up done");$
total: 3 errors, 10 warnings, 0 checks, 446 lines checked
Warning in drivers/bus/dpaa/dpaa_bus.c:
Using compiler attribute directly
parent reply other threads:[~2025-07-01 11:39 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250701113707.2793004-9-vanshika.shukla@nxp.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=20250701113743.49B801252DA@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=vanshika.shukla@nxp.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).