[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240205132600.GJ960600@kernel.org>
Date: Mon, 5 Feb 2024 13:26:00 +0000
From: Simon Horman <horms@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Colin Ian King <colin.i.king@...il.com>,
Tariq Toukan <tariqt@...dia.com>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
netdev@...r.kernel.org, linux-rdma@...r.kernel.org,
kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH][next] mlx4: Fix spelling mistake: "mape" -> "map"
On Tue, Dec 12, 2023 at 01:19:13PM -0800, Jakub Kicinski wrote:
> On Tue, 12 Dec 2023 20:30:43 +0000 Simon Horman wrote:
> > On Sat, Dec 09, 2023 at 10:51:35PM +0000, Colin Ian King wrote:
> > > There is a spelling mistake in a mlx4_err error message. Fix it.
> > >
> > > Signed-off-by: Colin Ian King <colin.i.king@...il.com>
> >
> > Hi Colin,
> >
> > I am guessing that you are focusing on error messages and other user-facing
> > spelling errors (perhaps you told me f2f in the hallway track at Kernel
> > Recipes). But I do wonder if you have plans to address other spelling
> > errors in this driver. codespell flags many, including 'segements' in a
> > comment in the same file.
>
> It'd be great to fix all the codespell issues with one path, IMO.
For the record, I have sent a follow up here:
- [PATCH net-nex] mlx4: Address spelling errors
https://lore.kernel.org/netdev/20240205-mlx5-codespell-v1-1-63b86dffbb61@kernel.org/
Powered by blists - more mailing lists