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>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.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 mistakes in mlx5_core_dbg message and comments
Date: Fri, 18 Apr 2025 22:04:22 +0300 [thread overview]
Message-ID: <d72ba588-65f6-4ef0-888d-fb7032ca6553@nvidia.com> (raw)
In-Reply-To: <20250418135703.542722-1-colin.i.king@gmail.com>
On 18/04/2025 16:57, Colin Ian King wrote:
> There is a spelling mistake in a mlx5_core_dbg and two spelling mistakes
> in comment blocks. Fix them.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> drivers/net/ethernet/mellanox/mlx5/core/pci_irq.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/pci_irq.c b/drivers/net/ethernet/mellanox/mlx5/core/pci_irq.c
> index 2c5f850c31f6..40024cfa3099 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/core/pci_irq.c
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/pci_irq.c
> @@ -148,7 +148,7 @@ int mlx5_set_msix_vec_count(struct mlx5_core_dev *dev, int function_id,
> * Free the IRQ and other resources such as rmap from the system.
> * BUT doesn't free or remove reference from mlx5.
> * This function is very important for the shutdown flow, where we need to
> - * cleanup system resoruces but keep mlx5 objects alive,
> + * cleanup system resources but keep mlx5 objects alive,
> * see mlx5_irq_table_free_irqs().
> */
> static void mlx5_system_free_irq(struct mlx5_irq *irq)
> @@ -588,7 +588,7 @@ static void irq_pool_free(struct mlx5_irq_pool *pool)
> struct mlx5_irq *irq;
> unsigned long index;
>
> - /* There are cases in which we are destrying the irq_table before
> + /* There are cases in which we are destroying the irq_table before
> * freeing all the IRQs, fast teardown for example. Hence, free the irqs
> * which might not have been freed.
> */
> @@ -617,7 +617,7 @@ static int irq_pools_init(struct mlx5_core_dev *dev, int sf_vec, int pcif_vec,
> if (!mlx5_sf_max_functions(dev))
> return 0;
> if (sf_vec < MLX5_IRQ_VEC_COMP_BASE_SF) {
> - mlx5_core_dbg(dev, "Not enught IRQs for SFs. SF may run at lower performance\n");
> + mlx5_core_dbg(dev, "Not enough IRQs for SFs. SF may run at lower performance\n");
> return 0;
> }
>
Acked-by: Mark Bloch <mbloch@nvidia.com>
Thanks
next prev parent reply other threads:[~2025-04-18 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 13:57 [PATCH][next] net/mlx5: Fix spelling mistakes in mlx5_core_dbg message and comments Colin Ian King
2025-04-18 19:04 ` Mark Bloch [this message]
2025-04-22 9:10 ` 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=d72ba588-65f6-4ef0-888d-fb7032ca6553@nvidia.com \
--to=mbloch@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=colin.i.king@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@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