From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Dongdong Liu <liudongdong3@huawei.com>
Subject: |WARNING| pw126988 [PATCH 5/5] net/hns3: add Tx/Rx descriptor logs
Date: Thu, 18 May 2023 13:34:26 +0200 (CEST) [thread overview]
Message-ID: <20230518113426.86BB4120927@dpdk.org> (raw)
In-Reply-To: <20230518112944.32276-6-liudongdong3@huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/126988
_coding style issues_
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'rxdp' - possible side-effects?
#148: FILE: drivers/net/hns3/hns3_rxtx.h:556:
+#define RX_BD_LOG(hw, level, rxdp) \
+ PMD_RX_LOG(hw, level, "Rx descriptor: " \
+ "l234_info=%#x pkt_len=%u size=%u rss_hash=%#x fd_id=%u vlan_tag=%u " \
+ "o_dm_vlan_id_fb=%#x ot_vlan_tag=%u bd_base_info=%#x", \
+ rte_le_to_cpu_32((rxdp)->rx.l234_info), \
+ rte_le_to_cpu_16((rxdp)->rx.pkt_len), \
+ rte_le_to_cpu_16((rxdp)->rx.size), \
+ rte_le_to_cpu_32((rxdp)->rx.rss_hash), \
+ rte_le_to_cpu_16((rxdp)->rx.fd_id), \
+ rte_le_to_cpu_16((rxdp)->rx.vlan_tag), \
+ rte_le_to_cpu_16((rxdp)->rx.o_dm_vlan_id_fb), \
+ rte_le_to_cpu_16((rxdp)->rx.ot_vlan_tag), \
+ rte_le_to_cpu_32((rxdp)->rx.bd_base_info))
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'txdp' - possible side-effects?
#162: FILE: drivers/net/hns3/hns3_rxtx.h:570:
+#define TX_BD_LOG(hw, level, txdp) \
+ PMD_TX_LOG(hw, level, "Tx descriptor: " \
+ "vlan_tag=%u send_size=%u type_cs_vlan_tso_len=%#x outer_vlan_tag=%u " \
+ "tv=%#x ol_type_vlan_len_msec=%#x paylen_fd_dop_ol4cs=%#x " \
+ "tp_fe_sc_vld_ra_ri=%#x ckst_mss=%u", \
+ rte_le_to_cpu_16((txdp)->tx.vlan_tag), \
+ rte_le_to_cpu_16((txdp)->tx.send_size), \
+ rte_le_to_cpu_32((txdp)->tx.type_cs_vlan_tso_len), \
+ rte_le_to_cpu_16((txdp)->tx.outer_vlan_tag), \
+ rte_le_to_cpu_16((txdp)->tx.tv), \
+ rte_le_to_cpu_32((txdp)->tx.ol_type_vlan_len_msec), \
+ rte_le_to_cpu_32((txdp)->tx.paylen_fd_dop_ol4cs), \
+ rte_le_to_cpu_16((txdp)->tx.tp_fe_sc_vld_ra_ri), \
+ rte_le_to_cpu_16((txdp)->tx.ckst_mss))
total: 0 errors, 0 warnings, 2 checks, 88 lines checked
next prev parent reply other threads:[~2023-05-18 11:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230518112944.32276-6-liudongdong3@huawei.com>
2023-05-18 11:21 ` |SUCCESS| pw126984-126988 " qemudev
2023-05-18 11:25 ` qemudev
2023-05-18 11:34 ` checkpatch [this message]
2023-05-18 20:20 ` |SUCCESS| pw126988 " 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=20230518113426.86BB4120927@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=liudongdong3@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).