From: Simon Horman <horms@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Colin Ian King <colin.i.king@gmail.com>,
Tariq Toukan <tariqt@nvidia.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] mlx4: Fix spelling mistake: "mape" -> "map"
Date: Mon, 5 Feb 2024 13:26:00 +0000 [thread overview]
Message-ID: <20240205132600.GJ960600@kernel.org> (raw)
In-Reply-To: <20231212131913.4195bc38@kernel.org>
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@gmail.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/
next prev parent reply other threads:[~2024-02-05 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 22:51 [PATCH][next] mlx4: Fix spelling mistake: "mape" -> "map" Colin Ian King
2023-12-12 20:30 ` Simon Horman
2023-12-12 21:19 ` Jakub Kicinski
2024-02-05 13:26 ` Simon Horman [this message]
2023-12-12 21:55 ` Colin King (gmail)
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=20240205132600.GJ960600@kernel.org \
--to=horms@kernel.org \
--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=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.