From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-test-report] |WARNING| pw52211 [RFC 1/5] eal: add accessor functions for lcore_config
Date: Wed, 3 Apr 2019 19:17:44 +0200 (CEST) [thread overview]
Message-ID: <20190403171744.29E101B54C@dpdk.org> (raw)
In-Reply-To: <20190403171610.23970-2-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/52211
_coding style issues_
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#80: FILE: lib/librte_eal/common/eal_common_lcore.c:41:
+rte_cpuset_t rte_lcore_cpuset(unsigned lcore_id)
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#92: FILE: lib/librte_eal/common/eal_common_lcore.c:53:
+rte_lcore_state(unsigned lcore_id)
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#98: FILE: lib/librte_eal/common/eal_common_lcore.c:59:
+rte_lcore_return_code(unsigned lcore_id)
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#137: FILE: lib/librte_eal/common/include/rte_lcore.h:172:
+unsigned rte_lcore_to_socket_id(unsigned lcore_id);
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#137: FILE: lib/librte_eal/common/include/rte_lcore.h:172:
+unsigned rte_lcore_to_socket_id(unsigned lcore_id);
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#156: FILE: lib/librte_eal/common/include/rte_lcore.h:191:
+rte_cpuset_t rte_lcore_cpuset(unsigned lcore_id);
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#167: FILE: lib/librte_eal/common/include/rte_lcore.h:202:
+rte_lcore_return_code(unsigned lcore_id);
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#184: FILE: lib/librte_eal/common/include/rte_lcore.h:231:
+rte_lcore_state(unsigned lcore_id);
total: 0 errors, 8 warnings, 140 lines checked
parent reply other threads:[~2019-04-03 17:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20190403171610.23970-2-stephen@networkplumber.org>]
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=20190403171744.29E101B54C@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).