From: Mark Bloch <mbloch@nvidia.com>
To: Colin Ian King <colin.i.king@gmail.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
Tariq Toukan <tariqt@nvidia.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Cosmin Ratiu <cratiu@nvidia.com>,
Carolina Jubran <cjubran@nvidia.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] net/mlx5: Fix spelling mistake "disabliing" -> "disabling"
Date: Mon, 7 Jul 2025 11:27:37 +0300 [thread overview]
Message-ID: <f8ba8303-0ad8-4c93-b296-2bd96e1982fe@nvidia.com> (raw)
In-Reply-To: <20250703102219.1248399-1-colin.i.king@gmail.com>
On 03/07/2025 13:22, Colin Ian King wrote:
> There is a spelling mistake in a NL_SET_ERR_MSG_MOD message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> drivers/net/ethernet/mellanox/mlx5/core/esw/qos.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/esw/qos.c b/drivers/net/ethernet/mellanox/mlx5/core/esw/qos.c
> index 154bbb17ec0e..7ca6bba24001 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/core/esw/qos.c
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/esw/qos.c
> @@ -1353,7 +1353,7 @@ static int esw_qos_switch_tc_arbiter_node_to_vports(
> &node->ix);
> if (err) {
> NL_SET_ERR_MSG_MOD(extack,
> - "Failed to create scheduling element for vports node when disabliing vports TC QoS");
> + "Failed to create scheduling element for vports node when disabling vports TC QoS");
> return err;
> }
>
Reviewed-by: Mark Bloch <mbloch@nvidia.com>
Thanks for the fix.
next prev parent reply other threads:[~2025-07-07 8:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 10:22 [PATCH][next] net/mlx5: Fix spelling mistake "disabliing" -> "disabling" Colin Ian King
2025-07-07 8:27 ` Mark Bloch [this message]
2025-07-08 15:40 ` patchwork-bot+netdevbpf
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=f8ba8303-0ad8-4c93-b296-2bd96e1982fe@nvidia.com \
--to=mbloch@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=cjubran@nvidia.com \
--cc=colin.i.king@gmail.com \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@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