|author||Martin Olsson <firstname.lastname@example.org>||2009-04-23 11:37:37 +0200|
|committer||Jiri Kosina <email@example.com>||2009-06-12 18:01:46 +0200|
trivial: fix typo milisecond/millisecond for documentation and source comments.
Signed-off-by: Martin Olsson <firstname.lastname@example.org> Signed-off-by: Jiri Kosina <email@example.com>
Diffstat (limited to 'Documentation/CodingStyle')
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/CodingStyle b/Documentation/CodingStyle
index 72968cd5eaf..8bb37237ebd 100644
@@ -698,8 +698,8 @@ very often is not. Abundant use of the inline keyword leads to a much bigger
kernel, which in turn slows the system as a whole down, due to a bigger
icache footprint for the CPU and simply because there is less memory
available for the pagecache. Just think about it; a pagecache miss causes a
-disk seek, which easily takes 5 miliseconds. There are a LOT of cpu cycles
-that can go into these 5 miliseconds.
+disk seek, which easily takes 5 milliseconds. There are a LOT of cpu cycles
+that can go into these 5 milliseconds.
A reasonable rule of thumb is to not put inline at functions that have more
than 3 lines of code in them. An exception to this rule are the cases where