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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 11 Apr 2019 08:37:18 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Kenny Van de Maele <kenny.vandemaele@...its.eu>,
        torvalds@...ux-foundation.org
Cc:     torvalds@...l.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] <global> global spelling corrections for v5.1.0-rc5

On 4/11/19 8:00 AM, Kenny Van de Maele wrote:
> On Thu, 2019-04-11 at 07:58 -0700, Randy Dunlap wrote:
>> On 4/11/19 2:12 AM, Kenny Van de Maele wrote:
>>> are available in the Git repository at:
>>>
>>>   git://github.com/vdmkenny/linux-spelling-fix.git tags/common-
>>> spelling-fixes-5.1.0-rc5
>>>
>>> for you to fetch changes up to
>>> 6ee0055f3414a64133228e82004ea60d0e659d6d:
>>>
>>>   fix common spelling mistakes (2019-04-11 10:22:24 +0200)
>>>
>>> ----------------------------------------------------------------
>>> This PR contains a set of global spelling fixes of commonly miss-
>>> spelled
>>
>> misspelled
> 
> Bad joke :)
> 
>>
>>
>> Is there a way for me to review the diff on github?
> 
> https://github.com/vdmkenny/linux-spelling-fix/commit/6ee0055f3414a64133228e82004ea60d0e659d6d
> 
>>
>> thanks.
>>
>>
>>> words. Mostly documentation and comments were impacted, but a few
>>> lines
>>> of code were affected as well.
>>>
>>> ----------------------------------------------------------------
>>> Kenny Van de Maele (1):
>>>       fix common spelling mistakes
>>
>>


recheck this one also:

 drivers/net/wireless/intel/iwlwifi/fw/api/time-event.h
@@ -204,7 +204,7 @@ enum {
 * notification the status is always success. There is no start/end fragment
 * notification for monolithic events.
 *
- * @TE_V2_DEFAULT_POLICY: independent, social, present, unoticable
+ * @TE_V2_DEFAULT_POLICY: independent, social, present, unoticeable
 * @TE_V2_NOTIF_HOST_EVENT_START: request/receive notification on event start
 * @TE_V2_NOTIF_HOST_EVENT_END:request/receive notification on event end
 * @TE_V2_NOTIF_INTERNAL_EVENT_START: internal FW use



-- 
~Randy

Powered by blists - more mailing lists