Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Tariq Toukan <tariqt@nvidia.com>
To: Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>, <netdev@vger.kernel.org>,
	Paolo Abeni <pabeni@redhat.com>
Cc: Gal Pressman <gal@nvidia.com>, Jonathan Corbet <corbet@lwn.net>,
	"Leon Romanovsky" <leon@kernel.org>, <linux-doc@vger.kernel.org>,
	<linux-rdma@vger.kernel.org>, Mark Bloch <mbloch@nvidia.com>,
	Nimrod Oren <noren@nvidia.com>,
	Rahul Rameshbabu <rrameshbabu@nvidia.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Saeed Mahameed <saeedm@nvidia.com>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Simon Horman <horms@kernel.org>, Tariq Toukan <tariqt@nvidia.com>
Subject: [PATCH net-next 2/2] net/mlx5e: Fix incorrect name of rx_symbol_err_phy counter in documentation
Date: Fri, 20 Nov 2026 10:30:48 +0200	[thread overview]
Message-ID: <20261120083050.2540739-3-tariqt@nvidia.com> (raw)
In-Reply-To: <20261120083050.2540739-1-tariqt@nvidia.com>

From: Gal Pressman <gal@nvidia.com>

rx_symbol_err_phy was incorrectly referenced as rx_symbol_error_phy in
the rx_crc_errors_phy description, fix it.

Fixes: 8ce3b586faa4 ("net/mlx5: Add counter information to mlx5 driver documentation")
Signed-off-by: Gal Pressman <gal@nvidia.com>
Reviewed-by: Nimrod Oren <noren@nvidia.com>
Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
---
 .../device_drivers/ethernet/mellanox/mlx5/counters.rst          | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/counters.rst b/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/counters.rst
index 026259ae383c..de8d1a2bcdbe 100644
--- a/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/counters.rst
+++ b/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/counters.rst
@@ -930,7 +930,7 @@ like flow control, FEC and more.
    * - `rx_crc_errors_phy`
      - The number of dropped received packets due to FCS (Frame Check Sequence)
        error on the physical port. If this counter is increased in high rate,
-       check the link quality using `rx_symbol_error_phy` and
+       check the link quality using `rx_symbol_err_phy` and
        `rx_corrected_bits_phy` counters below.
      - Error
 
-- 
2.44.0


  parent reply	other threads:[~2026-11-20  8:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-20  8:30 [PATCH net-next 0/2] net/mlx5e: Fix mlx5e counters documentation errors Tariq Toukan
2026-11-20  8:30 ` [PATCH net-next 1/2] net/mlx5e: Remove documentation of nonexistent counters Tariq Toukan
2026-11-20  8:34   ` sashiko-bot
2026-11-20  8:30 ` Tariq Toukan [this message]
2026-11-20  8:34   ` [PATCH net-next 2/2] net/mlx5e: Fix incorrect name of rx_symbol_err_phy counter in documentation 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=20261120083050.2540739-3-tariqt@nvidia.com \
    --to=tariqt@nvidia.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=gal@nvidia.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=noren@nvidia.com \
    --cc=pabeni@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=rrameshbabu@nvidia.com \
    --cc=saeedm@nvidia.com \
    --cc=skhan@linuxfoundation.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