From: Joe Perches <joe@perches.com>
To: Colin King <colin.king@canonical.com>
Cc: linux-kernel@vger.kernel.org
Subject: typos in the tree
Date: Sun, 04 Jun 2017 12:44:29 -0700 [thread overview]
Message-ID: <1496605469.15643.6.camel@perches.com> (raw)
In-Reply-To: <20170604163608.24894-1-colin.king@canonical.com>
Just fyi, these are the most common typos that checkpatch shows
for linux-next as of 5/9
121 prefered
117 acknowledgement
103 informations
90 occured
67 endianess
60 Interrup
53 transfered
49 preemptable
47 struc
44 commited
43 childs
42 overriden
41 capabilites
37 sucess
35 splitted
34 programm
32 calle
32 adress
30 alow
28 paramaters
27 specfic
27 interupt
26 timout
25 specifc
25 ment
25 dependant
25 accomodate
23 seperate
23 continous
23 beeing
22 wether
22 ouput
22 Acknowledgement
21 retrive
21 avaiable
20 orignal
20 defintion
19 reseting
19 alignement
18 managment
18 defintions
17 syncronized
17 singal
17 paramters
17 actived
16 offet
16 lenght
16 immediatly
16 explict
16 explicitely
15 Regsiter
15 lengh
15 completition
15 cacluated
14 tranfer
14 paramter
14 hander
14 auxillary
13 ture
13 seperately
13 ressources
13 reqeust
13 removeable
13 releated
13 recieved
13 funtions
13 existant
12 targetting
12 preceeding
12 Optionnal
12 interrup
12 inteface
12 controled
12 contoller
12 Auxillary
12 aLow
11 writting
11 treshold
11 threshhold
11 segement
11 pathes
11 initalized
11 doesnt
11 convertor
10 upate
10 udpate
10 specifed
10 privilaged
10 paramater
10 mutiple
10 mergable
10 maxium
10 interrups
10 harware
10 halfs
10 defult
next prev parent reply other threads:[~2017-06-04 19:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 16:36 [PATCH] ath6kl: fix spelling mistake: "Indicat" -> "Indicate" Colin King
2017-06-04 19:44 ` Joe Perches [this message]
2017-06-05 0:47 ` Steve deRosier
2017-06-16 6:57 ` Kalle Valo
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=1496605469.15643.6.camel@perches.com \
--to=joe@perches.com \
--cc=colin.king@canonical.com \
--cc=linux-kernel@vger.kernel.org \
/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