summaryrefslogtreecommitdiffstats
path: root/Documentation/contributing/coding_style.md
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/contributing/coding_style.md')
-rw-r--r--Documentation/contributing/coding_style.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/contributing/coding_style.md b/Documentation/contributing/coding_style.md
index a8c7356bfebe..4980659cc0c0 100644
--- a/Documentation/contributing/coding_style.md
+++ b/Documentation/contributing/coding_style.md
@@ -801,7 +801,7 @@ 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 a parameter is known to be a compiletime constant, and as a
+cases where a parameter is known to be a compile time constant, and as a
result of this constantness you *know* the compiler will be able to
optimize most of your function away at compile time. For a good example
of this later case, see the kmalloc() inline function.