summaryrefslogtreecommitdiffstats
path: root/COPYING
diff options
context:
space:
mode:
authorKalin KOZHUHAROV <kalin@thinrope.net>2006-04-01 01:41:22 +0200
committerAdrian Bunk <bunk@stusta.de>2006-04-01 01:41:22 +0200
commit8ba8e95ed14a2771bbcb43300feda094f298853e (patch)
tree8f487c4f31175eea531fbf7305c91819eca17bec /COPYING
parent36a891b67f95fd5e1442fc0f7f953809b94b3fbc (diff)
downloadlinux-8ba8e95ed14a2771bbcb43300feda094f298853e.tar.gz
linux-8ba8e95ed14a2771bbcb43300feda094f298853e.tar.bz2
linux-8ba8e95ed14a2771bbcb43300feda094f298853e.zip
Fix comments: s/granuality/granularity/
I was grepping through the code and some `grep ganularity -R .` didn't catch what I thought. Then looking closer I saw the term "granuality" used in only four places (in comments) and granularity in many more places describing the same idea. Some other facts: dictionary.com does not know such a word define:granuality on google is not found (and pages for granuality are mostly related to patches to the kernel) it has not been discussed as a term on LKML, AFAICS (=Can Search) To be consistent, I think granularity should be used everywhere. Signed-off-by: Kalin KOZHUHAROV <kalin@thinrope.net> Signed-off-by: Adrian Bunk <bunk@stusta.de>
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions