From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw138134 [RFC] eal: increase the number of availble file descriptors for MP
Date: Fri, 8 Mar 2024 19:55:24 +0100 (CET) [thread overview]
Message-ID: <20240308185524.292CE1223EF@dpdk.org> (raw)
In-Reply-To: <20240308185401.150651-1-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/138134
_coding style issues_
WARNING:TYPO_SPELLING: 'availble' may be misspelled - perhaps 'available'?
#65:
Subject: [RFC] eal: increase the number of availble file descriptors for MP
WARNING:TYPO_SPELLING: 'compatiable' may be misspelled - perhaps 'compatible'?
#90:
broken in that it won't allow adding a backwards compatiable
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#156: FILE: lib/eal/common/eal_common_proc.c:858:
+int rte_mp_sendmsg_V24(struct rte_mp_msg *msg);
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#204: FILE: lib/eal/common/eal_common_proc.c:1108:
+int rte_mp_request_sync_V24(struct rte_mp_msg *req, struct rte_mp_reply *reply,
WARNING:LINE_CONTINUATIONS: Avoid unnecessary line continuations
#225: FILE: lib/eal/common/eal_common_proc.c:1127:
+MAP_STATIC_SYMBOL(int rte_mp_request_sync(struct rte_mp_msg *req, \
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#250: FILE: lib/eal/common/eal_common_proc.c:1285:
+int rte_mp_request_async_V24(struct rte_mp_msg *req, const struct timespec *ts,
WARNING:LINE_CONTINUATIONS: Avoid unnecessary line continuations
#269: FILE: lib/eal/common/eal_common_proc.c:1303:
+MAP_STATIC_SYMBOL(int rte_mp_request_async(struct rte_mp_msg *req, \
WARNING:AVOID_EXTERNS: externs should be avoided in .c files
#290: FILE: lib/eal/common/eal_common_proc.c:1332:
+int rte_mp_reply_V24(struct rte_mp_msg *msg, const char *peer);
total: 0 errors, 8 warnings, 245 lines checked
ERROR: symbol rte_mp_reply is added in the DPDK_23 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_mp_request_async is added in the DPDK_23 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_mp_request_sync is added in the DPDK_23 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_mp_sendmsg is added in the DPDK_23 section, but is expected to be added in the EXPERIMENTAL section of the version map
next prev parent reply other threads:[~2024-03-08 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240308185401.150651-1-stephen@networkplumber.org>
2024-03-08 18:30 ` |FAILURE| " qemudev
2024-03-08 18:55 ` checkpatch [this message]
2024-03-08 19:23 ` 0-day Robot
2024-03-08 21:25 ` |FAILURE| pw138134 [PATCH] " 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=20240308185524.292CE1223EF@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=stephen@networkplumber.org \
--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).