From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Rahul Gupta <rahulgupt@linux.microsoft.com>
Subject: |WARNING| pw135939 [PATCH v2] eal: refactor rte_eal_init into sub-functions
Date: Wed, 17 Jan 2024 20:25:48 +0100 (CET) [thread overview]
Message-ID: <20240117192548.6D811122B9B@dpdk.org> (raw)
In-Reply-To: <1705519502-16164-1-git-send-email-rahulgupt@linux.microsoft.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/135939
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
WARNING:TYPO_SPELLING: 'dont' may be misspelled - perhaps 'don't'?
#132: FILE: app/test-pmd/testpmd.c:4569:
+ * if testpmd application dont want to know progress/status of
WARNING:TYPO_SPELLING: 'MASTER' may be misspelled - perhaps 'PRIMARY'?
#155: FILE: lib/eal/include/rte_eal.h:117:
+ * Its called from rte_eal_init() on MASTER lcore only and must NOT be directly
total: 0 errors, 2 warnings, 169 lines checked
Warning in lib/eal/include/rte_eal.h:
Using compiler attribute directly
__rte_experimental must appear alone on the line immediately preceding the return type of a function.
__rte_experimental must appear alone on the line immediately preceding the return type of a function.
__rte_experimental must appear alone on the line immediately preceding the return type of a function.
__rte_experimental must appear alone on the line immediately preceding the return type of a function.
Please only put __rte_experimental tags in headers (b/lib/eal/linux/eal.c)
Please only put __rte_experimental tags in headers (b/lib/eal/linux/eal.c)
__rte_experimental must appear alone on the line immediately preceding the return type of a function.
Please only put __rte_experimental tags in headers (b/lib/eal/linux/eal.c)
__rte_experimental must appear alone on the line immediately preceding the return type of a function.
Please only put __rte_experimental tags in headers (b/lib/eal/linux/eal.c)
__rte_experimental must appear alone on the line immediately preceding the return type of a function.
next prev parent reply other threads:[~2024-01-17 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1705519502-16164-1-git-send-email-rahulgupt@linux.microsoft.com>
2024-01-17 19:07 ` |SUCCESS| " qemudev
2024-01-17 19:12 ` |FAILURE| " qemudev
2024-01-17 19:25 ` checkpatch [this message]
2024-01-17 20:18 ` |FAILURE| pw135939 [dpdk-dev] " 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=20240117192548.6D811122B9B@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=rahulgupt@linux.microsoft.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).