From: sashiko-bot@kernel.org
To: "Yanze Zhang" <zhang.yanze@zte.com.cn>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH rdma v9 1/7] RDMA/zrdma: Add build infrastructure and module skeleton
Date: Tue, 03 Nov 2026 13:20:14 +0000 [thread overview]
Message-ID: <sashiko-outbox-195324@kernel.org> (raw)
In-Reply-To: <20261103125654.2707069-2-zhang.yanze@zte.com.cn>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] RDMA/zrdma: open-coded zrdma_module_init() instead of module_auxiliary_driver()
--
commit 752d6c4a965c859c6d742178ece9515bf23454aa
Author: Yanze Zhang <zhang.yanze@zte.com.cn>
RDMA/zrdma: Add build infrastructure and module skeleton
This commit adds the MAINTAINERS entry, Kconfig, Makefile, and a minimal
auxiliary driver module skeleton for the ZTE DingHai RDMA driver.
> diff --git a/drivers/infiniband/hw/zrdma/zrdma_main.c b/drivers/infiniband/hw/zrdma/zrdma_main.c
> new file mode 100644
> index 0000000000000..80856c7ff6b2a
> --- /dev/null
> +++ b/drivers/infiniband/hw/zrdma/zrdma_main.c
[ ... ]
> +static struct auxiliary_driver zxdh_auxiliary_drv = {
> + .name = "rdma_aux",
> + .id_table = zxdh_auxiliary_id_table,
> + .probe = zxdh_probe,
> + .remove = zxdh_remove,
> +};
> +
> +static int __init zrdma_module_init(void)
> +{
> + return auxiliary_driver_register(&zxdh_auxiliary_drv);
> +}
> +
> +static void __exit zrdma_module_exit(void)
> +{
> + auxiliary_driver_unregister(&zxdh_auxiliary_drv);
> +}
> +
> +module_init(zrdma_module_init);
> +module_exit(zrdma_module_exit);
[Severity: Low]
As reported by Sashiko on v8 [1], this isn't a bug, but since
zrdma_module_init() and zrdma_module_exit() only call
auxiliary_driver_register() and auxiliary_driver_unregister() on
zxdh_auxiliary_drv (including at the end of the patch series), could these
wrappers be replaced with module_auxiliary_driver(zxdh_auxiliary_drv) from
include/linux/auxiliary_bus.h?
[1] https://lore.kernel.org/r/20261102082026.2645777-2-zhang.yanze@zte.com.cn
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261103125654.2707069-1-zhang.yanze@zte.com.cn?part=1
next prev parent reply other threads:[~2026-11-03 13:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 12:56 [PATCH rdma v9 0/7] Add ZTE DingHai Ethernet Protocol Driver for RDMA Yanze Zhang
2026-11-03 12:56 ` [PATCH rdma v9 1/7] RDMA/zrdma: Add build infrastructure and module skeleton Yanze Zhang
2026-11-03 13:20 ` sashiko-bot [this message]
2026-11-03 12:56 ` [PATCH rdma v9 2/7] RDMA/zrdma: Add core data structures and ABI definitions Yanze Zhang
2026-11-03 13:19 ` sashiko-bot
2026-11-03 12:56 ` [PATCH rdma v9 3/7] RDMA/zrdma: Add internal headers and hardware register definitions Yanze Zhang
2026-11-03 13:18 ` sashiko-bot
2026-11-03 12:56 ` [PATCH rdma v9 4/7] RDMA/zrdma: Add hardware resource initialization and verbs skeleton Yanze Zhang
2026-11-03 13:21 ` sashiko-bot
2026-11-03 12:56 ` [PATCH rdma v9 5/7] RDMA/zrdma: Implement device and port query operations Yanze Zhang
2026-11-03 13:25 ` sashiko-bot
2026-11-03 12:56 ` [PATCH rdma v9 6/7] RDMA/zrdma: Add device probe and remove logic Yanze Zhang
2026-11-03 13:17 ` sashiko-bot
2026-11-03 12:56 ` [PATCH rdma v9 7/7] RDMA/zrdma: Implement context, PD, and mmap operations Yanze Zhang
2026-11-03 13:23 ` sashiko-bot
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=sashiko-outbox-195324@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=zhang.yanze@zte.com.cn \
/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