From: "Colin King (gmail)" <colin.i.king@gmail.com>
To: Simon Horman <horms@kernel.org>
Cc: Tariq Toukan <tariqt@nvidia.com>,
"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,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] mlx4: Fix spelling mistake: "mape" -> "map"
Date: Tue, 12 Dec 2023 21:55:51 +0000 [thread overview]
Message-ID: <b4f22a3b-3cab-4c0d-b4b9-700c58b62826@gmail.com> (raw)
In-Reply-To: <20231212203043.GF5817@kernel.org>
On 12/12/2023 20:30, 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.
Yes, there are so many trivial spelling mistakes and typos across the
kernel that I'm just focusing on user facing error messages for the moment.
Colin
>
> In any case,
>
> Reviewed-by: Simon Horman <horms@kernel.org>
prev parent reply other threads:[~2023-12-12 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 22:51 Colin Ian King
2023-12-12 20:30 ` Simon Horman
2023-12-12 21:19 ` Jakub Kicinski
2024-02-05 13:26 ` Simon Horman
2023-12-12 21:55 ` Colin King (gmail) [this message]
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=b4f22a3b-3cab-4c0d-b4b9-700c58b62826@gmail.com \
--to=colin.i.king@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome