From: netdev-bot+sashiko@kernel.org
To: tariqt@nvidia.com
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
cjubran@nvidia.com, gal@nvidia.com, linux-kernel@vger.kernel.org,
shshitrit@nvidia.com, leon@kernel.org, mbloch@nvidia.com,
saeedm@nvidia.com, dtatulea@nvidia.com, horms@kernel.org
Subject: Re: [PATCH net-next V2 5/5] net/mlx5: nodnic: Add health monitoring
Date: Mon, 12 Oct 2026 17:19:49 +0000 [thread overview]
Message-ID: <179182558993.434549.14029169550800193089@kernel.org> (raw)
In-Reply-To: <20261008171821.660739-6-tariqt@nvidia.com>
Thank you for your contribution! Sashiko AI review found more severe
issue(s) in other patches of this series. This mail is only an FYI, in case
you want to address the nit picks below when you respin.
Low priority / nit picks for your consideration:
- [Low] The patch removes the trailing newline from
drivers/net/ethernet/mellanox/mlx5/nodnic/Makefile.
--
net/mlx5: nodnic: Add health monitoring
This commit adds firmware health monitoring to the nodnic driver. A timer
periodically polls the health buffer in the initialization segment. It
detects fatal sensors, stalls in the health counter, and syndrome changes.
Polling is started from probe and stopped in remove.
> diff --git a/drivers/net/ethernet/mellanox/mlx5/nodnic/Makefile b/drivers/net/ethernet/mellanox/mlx5/nodnic/Makefile
> index 25865d7244d82..1d09edeaf3af8 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/nodnic/Makefile
> +++ b/drivers/net/ethernet/mellanox/mlx5/nodnic/Makefile
> @@ -5,4 +5,4 @@
>
> obj-$(CONFIG_MLX5_NODNIC) += mlx5_nodnic.o
>
> -mlx5_nodnic-y := main.o en.o en_cfg.o tx.o rx.o nodnic_pci_vsc.o
> +mlx5_nodnic-y := main.o en.o en_cfg.o tx.o rx.o nodnic_pci_vsc.o health.o
> \ No newline at end of file
[Severity: Low]
This isn't a bug, but the trailing newline at the end of the nodnic
Makefile has been dropped. Before this patch the mlx5_nodnic-y line ended
with a newline. Could it be put back so that checkpatch doesn't warn and
the next change to this file doesn't show an unrelated whitespace hunk?
[ ... ]
--
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261008171821.660739-1-tariqt%40nvidia.com
prev parent reply other threads:[~2026-10-12 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 17:18 [PATCH net-next V2 0/5] net/mlx5: Introduce mlx5_nodnic, a driver for DRAM-less NVIDIA Mellanox NIC functions Tariq Toukan
2026-10-08 17:18 ` [PATCH net-next V2 1/5] net/mlx5: nodnic: Introduce the mlx5_nodnic driver Tariq Toukan
2026-10-12 17:19 ` netdev-bot+sashiko
2026-10-08 17:18 ` [PATCH net-next V2 2/5] net/mlx5: nodnic: Implement data path Tariq Toukan
2026-10-12 17:19 ` netdev-bot+sashiko
2026-10-08 17:18 ` [PATCH net-next V2 3/5] net/mlx5: nodnic: Add TX/RX statistics Tariq Toukan
2026-10-12 17:19 ` netdev-bot+sashiko
2026-10-08 17:18 ` [PATCH net-next V2 4/5] net/mlx5: nodnic: Add ethtool driver info Tariq Toukan
2026-10-08 17:18 ` [PATCH net-next V2 5/5] net/mlx5: nodnic: Add health monitoring Tariq Toukan
2026-10-12 17:19 ` netdev-bot+sashiko [this message]
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=179182558993.434549.14029169550800193089@kernel.org \
--to=netdev-bot+sashiko@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=cjubran@nvidia.com \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=shshitrit@nvidia.com \
--cc=tariqt@nvidia.com \
/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
all inboxes | Powered by JetHome®