From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andre Muezerie <andremue@linux.microsoft.com>
Subject: |WARNING| pw152889 [PATCH 4/4] drivers: use macro to embed information in binaries
Date: Fri, 11 Apr 2025 21:40:55 +0200 (CEST) [thread overview]
Message-ID: <20250411194055.B9E7E1240EC@dpdk.org> (raw)
In-Reply-To: <1744400374-26620-5-git-send-email-andremue@linux.microsoft.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/152889
_coding style issues_
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#453: FILE: drivers/bus/auxiliary/bus_auxiliary_driver.h:165:
+#define RTE_PMD_REGISTER_AUXILIARY(nm, auxiliary_drv, idx) \
RTE_INIT(auxiliaryinitfn_ ##nm) \
{ \
(auxiliary_drv).driver.name = RTE_STR(nm); \
rte_auxiliary_register(&(auxiliary_drv)); \
} \
+ RTE_PMD_EXPORT_NAME(nm, idx)
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#483: FILE: drivers/bus/cdx/bus_cdx_driver.h:149:
+#define RTE_PMD_REGISTER_CDX(nm, cdx_drv, idx) \
RTE_INIT(cdxinitfn_ ##nm) \
{\
(cdx_drv).driver.name = RTE_STR(nm);\
rte_cdx_register(&cdx_drv); \
} \
+ RTE_PMD_EXPORT_NAME(nm, idx)
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#503: FILE: drivers/bus/dpaa/bus_dpaa_driver.h:242:
+#define RTE_PMD_REGISTER_DPAA(nm, dpaa_drv, idx) \
RTE_INIT(dpaainitfn_ ##nm) \
{\
(dpaa_drv).driver.name = RTE_STR(nm);\
rte_dpaa_driver_register(&dpaa_drv); \
} \
+RTE_PMD_EXPORT_NAME(nm, idx)
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#523: FILE: drivers/bus/fslmc/bus_fslmc_driver.h:202:
+#define RTE_PMD_REGISTER_DPAA2(nm, dpaa2_drv, idx) \
RTE_INIT(dpaa2initfn_ ##nm) \
{\
(dpaa2_drv).driver.name = RTE_STR(nm);\
rte_fslmc_driver_register(&dpaa2_drv); \
} \
+RTE_PMD_EXPORT_NAME(nm, idx)
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#539: FILE: drivers/bus/fslmc/bus_fslmc_driver.h:233:
+#define RTE_PMD_REGISTER_DPAA2_OBJECT(nm, dpaa2_obj, idx) \
RTE_INIT(dpaa2objinitfn_ ##nm) \
{\
(dpaa2_obj).name = RTE_STR(nm);\
rte_fslmc_object_register(&dpaa2_obj); \
} \
+RTE_PMD_EXPORT_NAME(nm, idx)
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#621: FILE: drivers/bus/pci/bus_pci_driver.h:168:
+#define RTE_PMD_REGISTER_PCI(nm, pci_drv, idx) \
RTE_INIT(pciinitfn_ ##nm) \
{\
(pci_drv).driver.name = RTE_STR(nm);\
rte_pci_register(&pci_drv); \
} \
+RTE_PMD_EXPORT_NAME(nm, idx)
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#663: FILE: drivers/bus/uacce/bus_uacce_driver.h:242:
+#define RTE_PMD_REGISTER_UACCE(nm, uacce_drv, idx) \
RTE_INIT(uacceinitfn_ ##nm) \
{\
(uacce_drv).driver.name = RTE_STR(nm);\
rte_uacce_register(&uacce_drv); \
} \
+ RTE_PMD_EXPORT_NAME(nm, idx)
ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#705: FILE: drivers/bus/vmbus/bus_vmbus_driver.h:94:
+#define RTE_PMD_REGISTER_VMBUS(nm, vmbus_drv, idx) \
RTE_INIT(vmbusinitfn_ ##nm) \
{ \
(vmbus_drv).driver.name = RTE_STR(nm); \
rte_vmbus_register(&vmbus_drv); \
} \
+ RTE_PMD_EXPORT_NAME(nm, idx)
total: 8 errors, 0 warnings, 1486 lines checked
next prev parent reply other threads:[~2025-04-11 19:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1744400374-26620-5-git-send-email-andremue@linux.microsoft.com>
2025-04-11 19:12 ` |SUCCESS| pw152886-152889 " qemudev
2025-04-11 19:17 ` qemudev
2025-04-11 19:40 ` checkpatch [this message]
2025-04-11 20:10 ` |SUCCESS| pw152886-152889 [PATCH] [4/4] drivers: use macro to embed dpdklab
2025-04-11 20:22 ` |PENDING| " dpdklab
2025-04-11 20:24 ` dpdklab
2025-04-11 20:27 ` |SUCCESS| " dpdklab
2025-04-11 20:30 ` |PENDING| " dpdklab
2025-04-11 20:31 ` |SUCCESS| " dpdklab
2025-04-11 20:34 ` dpdklab
2025-04-11 20:37 ` |PENDING| " dpdklab
2025-04-11 20:38 ` dpdklab
2025-04-11 20:43 ` |SUCCESS| " dpdklab
2025-04-11 20:46 ` dpdklab
2025-04-11 20:50 ` dpdklab
2025-04-11 20:55 ` dpdklab
2025-04-11 21:03 ` |FAILURE| pw152889 [PATCH 4/4] drivers: use macro to embed information in binaries 0-day Robot
2025-04-11 21:10 ` |SUCCESS| pw152886-152889 [PATCH] [4/4] drivers: use macro to embed dpdklab
2025-04-11 21:28 ` dpdklab
2025-04-11 21:30 ` dpdklab
2025-04-11 21:30 ` dpdklab
2025-04-11 22:16 ` dpdklab
2025-04-11 22:35 ` dpdklab
2025-04-11 23:07 ` dpdklab
2025-04-11 23:27 ` 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=20250411194055.B9E7E1240EC@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=andremue@linux.microsoft.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).