automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Subject: |WARNING| pw137803 [RFC 2/7] eal: add generic bit manipulation macros
Date: Sat,  2 Mar 2024 15:03:24 +0100 (CET)	[thread overview]
Message-ID: <20240302140324.BD73E122335@dpdk.org> (raw)
In-Reply-To: <20240302135328.531940-3-mattias.ronnblom@ericsson.com>

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

_coding style issues_


ERROR:SPACING: need consistent spacing around '*' (ctx:WxO)
#147: FILE: lib/eal/include/rte_bitops.h:127:
+		 uint32_t *: rte_bit_test32,		\
 		          ^

ERROR:SPACING: spaces required around that ':' (ctx:OxW)
#147: FILE: lib/eal/include/rte_bitops.h:127:
+		 uint32_t *: rte_bit_test32,		\
 		           ^

ERROR:SPACING: need consistent spacing around '*' (ctx:WxO)
#148: FILE: lib/eal/include/rte_bitops.h:128:
+		 uint64_t *: rte_bit_test64)(addr, nr)
 		          ^

ERROR:SPACING: spaces required around that ':' (ctx:OxW)
#148: FILE: lib/eal/include/rte_bitops.h:128:
+		 uint64_t *: rte_bit_test64)(addr, nr)
 		           ^

ERROR:SPACING: need consistent spacing around '*' (ctx:WxO)
#167: FILE: lib/eal/include/rte_bitops.h:147:
+		 uint32_t *: rte_bit_set32,		\
 		          ^

ERROR:SPACING: spaces required around that ':' (ctx:OxW)
#167: FILE: lib/eal/include/rte_bitops.h:147:
+		 uint32_t *: rte_bit_set32,		\
 		           ^

ERROR:SPACING: need consistent spacing around '*' (ctx:WxO)
#168: FILE: lib/eal/include/rte_bitops.h:148:
+		 uint64_t *: rte_bit_set64)(addr, nr)
 		          ^

ERROR:SPACING: spaces required around that ':' (ctx:OxW)
#168: FILE: lib/eal/include/rte_bitops.h:148:
+		 uint64_t *: rte_bit_set64)(addr, nr)
 		           ^

ERROR:SPACING: need consistent spacing around '*' (ctx:WxO)
#187: FILE: lib/eal/include/rte_bitops.h:167:
+		 uint32_t *: rte_bit_clear32,		\
 		          ^

ERROR:SPACING: spaces required around that ':' (ctx:OxW)
#187: FILE: lib/eal/include/rte_bitops.h:167:
+		 uint32_t *: rte_bit_clear32,		\
 		           ^

ERROR:SPACING: need consistent spacing around '*' (ctx:WxO)
#188: FILE: lib/eal/include/rte_bitops.h:168:
+		 uint64_t *: rte_bit_clear64)(addr, nr)
 		          ^

ERROR:SPACING: spaces required around that ':' (ctx:OxW)
#188: FILE: lib/eal/include/rte_bitops.h:168:
+		 uint64_t *: rte_bit_clear64)(addr, nr)
 		           ^

ERROR:SPACING: need consistent spacing around '*' (ctx:WxO)
#208: FILE: lib/eal/include/rte_bitops.h:188:
+		 uint32_t *: rte_bit_assign32,			\
 		          ^

ERROR:SPACING: spaces required around that ':' (ctx:OxW)
#208: FILE: lib/eal/include/rte_bitops.h:188:
+		 uint32_t *: rte_bit_assign32,			\
 		           ^

ERROR:SPACING: need consistent spacing around '*' (ctx:WxO)
#209: FILE: lib/eal/include/rte_bitops.h:189:
+		 uint64_t *: rte_bit_assign64)(addr, nr, value)
 		          ^

ERROR:SPACING: spaces required around that ':' (ctx:OxW)
#209: FILE: lib/eal/include/rte_bitops.h:189:
+		 uint64_t *: rte_bit_assign64)(addr, nr, value)
 		           ^

total: 16 errors, 0 warnings, 87 lines checked

           reply	other threads:[~2024-03-02 14:03 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20240302135328.531940-3-mattias.ronnblom@ericsson.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=20240302140324.BD73E122335@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=mattias.ronnblom@ericsson.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).