automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: |WARNING| pw120120 [PATCH 1/2] eal: provide leading and trailing zero bit count abstraction
Date: Wed, 23 Nov 2022 23:16:34 +0100 (CET)	[thread overview]
Message-ID: <20221123221634.B710212348D@dpdk.org> (raw)
In-Reply-To: <1669241687-18810-2-git-send-email-roretzla@linux.microsoft.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/120120

_coding style issues_


WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#111: FILE: lib/eal/include/rte_bitcount.h:31:
+	return (unsigned)rv;

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#133: FILE: lib/eal/include/rte_bitcount.h:53:
+	return (unsigned)rv;

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#155: FILE: lib/eal/include/rte_bitcount.h:75:
+	return (unsigned)rv;

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#177: FILE: lib/eal/include/rte_bitcount.h:97:
+	return (unsigned)rv;

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#199: FILE: lib/eal/include/rte_bitcount.h:119:
+	return (unsigned)rv;

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#221: FILE: lib/eal/include/rte_bitcount.h:141:
+	return (unsigned)rv;

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#241: FILE: lib/eal/include/rte_bitcount.h:161:
+	return (unsigned)__builtin_clz(v);

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#259: FILE: lib/eal/include/rte_bitcount.h:179:
+	return (unsigned)__builtin_clzl(v);

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#277: FILE: lib/eal/include/rte_bitcount.h:197:
+	return (unsigned)__builtin_clzll(v);

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#295: FILE: lib/eal/include/rte_bitcount.h:215:
+	return (unsigned)__builtin_ctz(v);

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#313: FILE: lib/eal/include/rte_bitcount.h:233:
+	return (unsigned)__builtin_ctzl(v);

WARNING:UNSPECIFIED_INT: Prefer 'unsigned int' to bare use of 'unsigned'
#331: FILE: lib/eal/include/rte_bitcount.h:251:
+	return (unsigned)__builtin_ctzll(v);

total: 0 errors, 12 warnings, 264 lines checked

           reply	other threads:[~2022-11-23 22:16 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1669241687-18810-2-git-send-email-roretzla@linux.microsoft.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=20221123221634.B710212348D@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=roretzla@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).