From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Anatoly Burakov <anatoly.burakov@intel.com>
Subject: [dpdk-test-report] |WARNING| pw87105 [PATCH v20 1/4] eal: rename power monitor condition member
Date: Fri, 22 Jan 2021 18:12:55 +0100 (CET) [thread overview]
Message-ID: <20210122171255.84E741E2B@dpdk.org> (raw)
In-Reply-To: <70f9d194e2714113c21a68da0fca93ff75e765d1.1611335511.git.anatoly.burakov@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/87105
_coding style issues_
ERROR:CODE_INDENT: code indent should use tabs where possible
#166: FILE: lib/librte_eal/include/generic/rte_power_intrinsics.h:24:
+^I * to by `addr` will be read and compared$
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#166: FILE: lib/librte_eal/include/generic/rte_power_intrinsics.h:24:
+ uint64_t val; /**< If the `mask` is non-zero, location pointed
+ * to by `addr` will be read and compared
ERROR:CODE_INDENT: code indent should use tabs where possible
#167: FILE: lib/librte_eal/include/generic/rte_power_intrinsics.h:25:
+^I * against this value.$
ERROR:CODE_INDENT: code indent should use tabs where possible
#168: FILE: lib/librte_eal/include/generic/rte_power_intrinsics.h:26:
+^I */$
ERROR:CODE_INDENT: code indent should use tabs where possible
#171: FILE: lib/librte_eal/include/generic/rte_power_intrinsics.h:29:
+^I * expected value (`val`) with data read from the$
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#171: FILE: lib/librte_eal/include/generic/rte_power_intrinsics.h:29:
+ uint8_t size; /**< Data size (in bytes) that will be used to compare
+ * expected value (`val`) with data read from the
ERROR:CODE_INDENT: code indent should use tabs where possible
#172: FILE: lib/librte_eal/include/generic/rte_power_intrinsics.h:30:
+^I * monitored memory location (`addr`). Can be 1, 2,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#173: FILE: lib/librte_eal/include/generic/rte_power_intrinsics.h:31:
+^I * 4, or 8. Supplying any other value will result in$
ERROR:CODE_INDENT: code indent should use tabs where possible
#174: FILE: lib/librte_eal/include/generic/rte_power_intrinsics.h:32:
+^I * an error.$
ERROR:CODE_INDENT: code indent should use tabs where possible
#175: FILE: lib/librte_eal/include/generic/rte_power_intrinsics.h:33:
+^I */$
total: 8 errors, 2 warnings, 81 lines checked
parent reply other threads:[~2021-01-22 17:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <70f9d194e2714113c21a68da0fca93ff75e765d1.1611335511.git.anatoly.burakov@intel.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=20210122171255.84E741E2B@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).