From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Anatoly Burakov <anatoly.burakov@intel.com>
Subject: |WARNING| pw143694 [RFC PATCH v1 5/5] lcore: store physical package ID internally
Date: Fri, 6 Sep 2024 13:48:36 +0200 (CEST) [thread overview]
Message-ID: <20240906114836.A196F121D10@dpdk.org> (raw)
In-Reply-To: <f68d303116b86fd1df004c43941c72444a697c9d.1725622420.git.anatoly.burakov@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/143694
_coding style issues_
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#181: FILE: lib/eal/common/eal_thread.h:39:
+unsigned eal_cpu_package_id(unsigned cpu_id);
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#181: FILE: lib/eal/common/eal_thread.h:39:
+unsigned eal_cpu_package_id(unsigned cpu_id);
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#195: FILE: lib/eal/freebsd/eal_lcore.c:45:
+eal_cpu_package_id(__rte_unused unsigned cpu_id)
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#227: FILE: lib/eal/linux/eal_lcore.c:65:
+eal_cpu_package_id(unsigned lcore_id)
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#234: FILE: lib/eal/linux/eal_lcore.c:72:
+ if (len <= 0 || (unsigned)len >= sizeof(path))
WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#238: FILE: lib/eal/linux/eal_lcore.c:76:
+ return (unsigned)id;
total: 0 errors, 6 warnings, 148 lines checked
next prev parent reply other threads:[~2024-09-06 11:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f68d303116b86fd1df004c43941c72444a697c9d.1725622420.git.anatoly.burakov@intel.com>
2024-09-06 11:21 ` |SUCCESS| pw143690-143694 " qemudev
2024-09-06 11:25 ` qemudev
2024-09-06 11:48 ` checkpatch [this message]
2024-09-06 12:44 ` |SUCCESS| pw143694 " 0-day Robot
2024-09-06 16:29 ` |SUCCESS| pw143690-143694 [PATCH] [RFC,v1,5/5] lcore: store physical dpdklab
2024-09-06 16:33 ` dpdklab
2024-09-06 16:41 ` |PENDING| " dpdklab
2024-09-06 16:44 ` |FAILURE| " dpdklab
2024-09-06 16:47 ` |PENDING| " dpdklab
2024-09-06 16:53 ` |FAILURE| " dpdklab
2024-09-06 16:59 ` |SUCCESS| " dpdklab
2024-09-06 17:01 ` dpdklab
2024-09-06 18:47 ` dpdklab
2024-09-06 19:39 ` |FAILURE| " dpdklab
2024-09-06 22:59 ` |SUCCESS| " dpdklab
2024-09-06 22:59 ` dpdklab
2024-09-07 2:27 ` dpdklab
2024-09-07 2:30 ` |FAILURE| " dpdklab
2024-09-07 2:34 ` dpdklab
2024-09-07 2:53 ` dpdklab
2024-09-07 2:56 ` dpdklab
2024-09-07 7:57 ` |PENDING| " dpdklab
2024-09-07 10:54 ` |FAILURE| " dpdklab
2024-09-07 17:28 ` |SUCCESS| " dpdklab
2024-09-08 3:06 ` dpdklab
2024-09-17 7:55 ` |FAILURE| " dpdklab
2024-09-17 8:15 ` |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=20240906114836.A196F121D10@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=anatoly.burakov@intel.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).