From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Kamil Vojanec <vojanec@cesnet.cz>
Subject: |WARNING| pw143196 [RFC] table: report victim replace stats in LRU tables
Date: Fri, 16 Aug 2024 13:59:56 +0200 (CEST) [thread overview]
Message-ID: <20240816115956.32A5F123EF6@dpdk.org> (raw)
In-Reply-To: <20240816115848.432547-1-vojanec@cesnet.cz>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/143196
_coding style issues_
WARNING:TYPO_SPELLING: 'happenning' may be misspelled - perhaps 'happening'?
#60:
is, however, no information about this happenning in either the return
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#93: FILE: lib/table/rte_table_hash_key16.c:30:
+#define RTE_TABLE_HASH_KEY16_STATS_PKTS_INSERT_VICTIMS_ADD(table, val) \
+ table->stats.n_pkts_insert_victims += val
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#120: FILE: lib/table/rte_table_hash_key32.c:30:
+#define RTE_TABLE_HASH_KEY32_STATS_PKTS_INSERT_VICTIMS_ADD(table, val) \
+ table->stats.n_pkts_insert_victims += val
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#147: FILE: lib/table/rte_table_hash_key8.c:28:
+#define RTE_TABLE_HASH_KEY8_STATS_PKTS_INSERT_VICTIMS_ADD(table, val) \
+ table->stats.n_pkts_insert_victims += val
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#174: FILE: lib/table/rte_table_hash_lru.c:26:
+#define RTE_TABLE_HASH_LRU_STATS_PKTS_INSERT_VICTIMS_ADD(table, val) \
+ table->stats.n_pkts_insert_victims += val
total: 4 errors, 1 warnings, 91 lines checked
next prev parent reply other threads:[~2024-08-16 11:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240816115848.432547-1-vojanec@cesnet.cz>
2024-08-16 11:32 ` |SUCCESS| " qemudev
2024-08-16 11:37 ` qemudev
2024-08-16 11:59 ` checkpatch [this message]
2024-08-16 12:42 ` |SUCCESS| pw143196 [PATCH] [RFC] table: report victim replace stats dpdklab
2024-08-16 12:43 ` dpdklab
2024-08-16 12:43 ` dpdklab
2024-08-16 12:44 ` dpdklab
2024-08-16 12:47 ` dpdklab
2024-08-16 12:47 ` dpdklab
2024-08-16 12:49 ` dpdklab
2024-08-16 12:50 ` dpdklab
2024-08-16 12:55 ` |PENDING| " dpdklab
2024-08-16 12:56 ` |SUCCESS| " dpdklab
2024-08-16 12:58 ` dpdklab
2024-08-16 12:58 ` dpdklab
2024-08-16 13:01 ` dpdklab
2024-08-16 13:01 ` dpdklab
2024-08-16 13:02 ` |SUCCESS| pw143196 [RFC] table: report victim replace stats in LRU tables 0-day Robot
2024-08-16 13:15 ` |SUCCESS| pw143196 [PATCH] [RFC] table: report victim replace stats dpdklab
2024-08-16 13:15 ` dpdklab
2024-08-16 13:17 ` dpdklab
2024-08-16 13:24 ` dpdklab
2024-08-16 13:30 ` |FAILURE| " dpdklab
2024-08-16 13:35 ` |SUCCESS| " dpdklab
2024-08-16 14:12 ` 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=20240816115956.32A5F123EF6@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=vojanec@cesnet.cz \
/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).