From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jie Hai <haijie1@huawei.com>
Subject: |WARNING| pw134898 [PATCH v2 4/4] net/hns3: use stdatomic API
Date: Thu, 7 Dec 2023 02:47:07 +0100 (CET) [thread overview]
Message-ID: <20231207014707.666D3121E42@dpdk.org> (raw)
In-Reply-To: <20231207014205.4002558-5-haijie1@huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/134898
_coding style issues_
CHECK:SPACING: No space is necessary after a cast
#83: FILE: drivers/net/hns3/hns3_cmd.c:47:
+ static RTE_ATOMIC(uint64_t) hns3_dma_memzone_id;
CHECK:SPACING: No space is necessary after a cast
#337: FILE: drivers/net/hns3/hns3_ethdev.h:402:
+ RTE_ATOMIC(uint16_t) schedule;
CHECK:SPACING: No space is necessary after a cast
#340: FILE: drivers/net/hns3/hns3_ethdev.h:404:
+ RTE_ATOMIC(uint16_t) resetting;
CHECK:SPACING: No space is necessary after a cast
#343: FILE: drivers/net/hns3/hns3_ethdev.h:406:
+ RTE_ATOMIC(uint16_t) disable_cmd;
CHECK:SPACING: No space is necessary after a cast
#348: FILE: drivers/net/hns3/hns3_ethdev.h:410:
+ RTE_ATOMIC(uint64_t) pending;
CHECK:SPACING: No space is necessary after a cast
#351: FILE: drivers/net/hns3/hns3_ethdev.h:412:
+ RTE_ATOMIC(uint64_t) request;
CHECK:SPACING: No space is necessary after a cast
#360: FILE: drivers/net/hns3/hns3_ethdev.h:500:
+ RTE_ATOMIC(unsigned int) secondary_cnt; /* Number of secondary processes init'd. */
CHECK:SPACING: No space is necessary after a cast
#369: FILE: drivers/net/hns3/hns3_ethdev.h:845:
+ RTE_ATOMIC(uint16_t) pf_push_lsc_cap;
CHECK:SPACING: No space is necessary after a cast
#378: FILE: drivers/net/hns3/hns3_ethdev.h:854:
+ RTE_ATOMIC(uint16_t) poll_job_started; /* whether poll job is started */
WARNING:FUNCTION_ARGUMENTS: function definition argument 'uint64_t *' should also have an identifier name
#804: FILE: drivers/net/hns3/hns3_intr.h:174:
+void hns3_handle_msix_error(struct hns3_adapter *hns, RTE_ATOMIC(uint64_t *)levels);
WARNING:FUNCTION_ARGUMENTS: function definition argument 'uint64_t *' should also have an identifier name
#805: FILE: drivers/net/hns3/hns3_intr.h:175:
+void hns3_handle_ras_error(struct hns3_adapter *hns, RTE_ATOMIC(uint64_t *)levels);
total: 0 errors, 2 warnings, 9 checks, 752 lines checked
next prev parent reply other threads:[~2023-12-07 1:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231207014205.4002558-5-haijie1@huawei.com>
2023-12-07 1:30 ` |SUCCESS| pw134895-134898 " qemudev
2023-12-07 1:35 ` qemudev
2023-12-07 1:47 ` checkpatch [this message]
2023-12-07 2:21 ` |FAILURE| pw134898 " 0-day Robot
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=20231207014707.666D3121E42@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=haijie1@huawei.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).