From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: longli@linuxonhyperv.com
Subject: |WARNING| pw151772 [Patch v3] net/mana: use mana_local_data for tracking usage data for primary process
Date: Fri, 21 Feb 2025 00:33:26 +0100 (CET) [thread overview]
Message-ID: <20250220233326.CA129127813@dpdk.org> (raw)
In-Reply-To: <1740094322-10919-1-git-send-email-longli@linuxonhyperv.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/151772
_coding style issues_
Must be a reply to the first patch (--in-reply-to).
WARNING:LONG_LINE: line length of 105 exceeds 100 columns
#117: FILE: drivers/net/mana/mana.c:1193:
+ rte_atomic_store_explicit(&mana_shared_data->secondary_cnt, 0, rte_memory_order_relaxed);
WARNING:LONG_LINE: line length of 109 exceeds 100 columns
#217: FILE: drivers/net/mana/mana.c:1578:
+ rte_atomic_fetch_add_explicit(&mana_shared_data->secondary_cnt, 1, rte_memory_order_relaxed);
WARNING:LONG_LINE: line length of 117 exceeds 100 columns
#265: FILE: drivers/net/mana/mana.c:1614:
+ RTE_VERIFY(rte_atomic_load_explicit(&mana_shared_data->secondary_cnt, rte_memory_order_relaxed) > 0);
WARNING:LONG_LINE: line length of 109 exceeds 100 columns
#266: FILE: drivers/net/mana/mana.c:1615:
+ rte_atomic_fetch_sub_explicit(&mana_shared_data->secondary_cnt, 1, rte_memory_order_relaxed);
CHECK:SPACING: No space is necessary after a cast
#296: FILE: drivers/net/mana/mana.h:12:
+ RTE_ATOMIC(uint32_t) secondary_cnt;
WARNING:LONG_LINE: line length of 102 exceeds 100 columns
#309: FILE: drivers/net/mana/mp.c:309:
+ if (rte_atomic_load_explicit(&mana_shared_data->secondary_cnt, rte_memory_order_relaxed) == 0)
total: 0 errors, 5 warnings, 1 checks, 212 lines checked
next prev parent reply other threads:[~2025-02-20 23:33 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1740094322-10919-1-git-send-email-longli@linuxonhyperv.com>
2025-02-20 23:03 ` |SUCCESS| " qemudev
2025-02-20 23:07 ` qemudev
2025-02-20 23:33 ` checkpatch [this message]
2025-02-21 0:44 ` 0-day Robot
2025-02-21 2:36 ` |SUCCESS| pw151772 [PATCH] [v3] net/mana: use mana_local_data for tr dpdklab
2025-02-21 2:37 ` dpdklab
2025-02-21 2:38 ` dpdklab
2025-02-21 2:41 ` dpdklab
2025-02-21 3:15 ` dpdklab
2025-02-21 3:21 ` dpdklab
2025-02-21 3:30 ` |PENDING| " dpdklab
2025-02-21 3:33 ` |SUCCESS| " dpdklab
2025-02-21 3:42 ` dpdklab
2025-02-21 3:44 ` dpdklab
2025-02-21 3:44 ` dpdklab
2025-02-21 3:56 ` |PENDING| " dpdklab
2025-02-21 4:10 ` dpdklab
2025-02-21 4:11 ` dpdklab
2025-02-21 4:28 ` |SUCCESS| " dpdklab
2025-02-21 4:46 ` |PENDING| " dpdklab
2025-02-21 4:48 ` dpdklab
2025-02-21 4:56 ` |SUCCESS| " dpdklab
2025-02-21 4:56 ` dpdklab
2025-02-21 5:10 ` dpdklab
2025-02-21 5:10 ` dpdklab
2025-02-21 5:11 ` dpdklab
2025-02-21 5:13 ` dpdklab
2025-02-21 5:27 ` dpdklab
2025-02-21 5:27 ` |PENDING| " dpdklab
2025-02-21 5:31 ` dpdklab
2025-02-21 5:39 ` |SUCCESS| " dpdklab
2025-02-21 6:07 ` dpdklab
2025-02-21 6:07 ` dpdklab
2025-02-21 6:23 ` dpdklab
2025-02-21 6:25 ` dpdklab
2025-02-21 6:55 ` dpdklab
2025-02-21 6:55 ` dpdklab
2025-02-21 6:56 ` dpdklab
2025-02-21 6:56 ` dpdklab
2025-02-21 7:32 ` dpdklab
2025-02-21 17:40 ` 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=20250220233326.CA129127813@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=longli@linuxonhyperv.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).