linux-kernel - Re: [PATCH][next] wifi: rtw89: mac: Fix spelling mistakes "notfify" -> "notify"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <75cd2090-857e-4082-bbc1-e3726235bda1@gmail.com>
Date: Fri, 22 Dec 2023 12:08:33 +0000
From: "Colin King (gmail)" <colin.i.king@...il.com>
To: Ping-Ke Shih <pkshih@...ltek.com>, Kalle Valo <kvalo@...nel.org>,
 "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>
Cc: "kernel-janitors@...r.kernel.org" <kernel-janitors@...r.kernel.org>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH][next] wifi: rtw89: mac: Fix spelling mistakes "notfify"
 -> "notify"

On 22/12/2023 00:19, Ping-Ke Shih wrote:
> 
> 
>> -----Original Message-----
>> From: Colin Ian King <colin.i.king@...il.com>
>> Sent: Wednesday, December 20, 2023 10:19 PM
>> To: Ping-Ke Shih <pkshih@...ltek.com>; Kalle Valo <kvalo@...nel.org>; linux-wireless@...r.kernel.org
>> Cc: kernel-janitors@...r.kernel.org; linux-kernel@...r.kernel.org
>> Subject: [PATCH][next] wifi: rtw89: mac: Fix spelling mistakes "notfify" -> "notify"
>>
>> There are two spelling mistakes in rtw89_err error messages. Fix these
>> and also add space between [ERR] and message text.
>>
>> Signed-off-by: Colin Ian King <colin.i.king@...il.com>
> 
> Acked-by: Ping-Ke Shih <pkshih@...ltek.com>
> 
> Thanks for the correctness. Could I know the tool you used to find out these
> typo?

Sure,

https://github.com/ColinIanKing/kernelscan

It needs the american dictionary, installed in /usr/share/dict e.g.
apt-get install wamerican

and then spellcheck with:

./kernelscan -k path-to-code-you-want-to-scan

I run kernelscan on the entire linux-next source daily and diff the 
days's results with the previous day using the meld diff tool.

Colin


> 
> Ping-Ke
> 
>