path: root/Documentation/CodingStyle
diff options
authorDan Carpenter <>2013-07-03 15:08:08 -0700
committerLinus Torvalds <>2013-07-03 16:08:01 -0700
commitb57a0505e750b3d7b2d39e9823b276d8ca1a08fe (patch)
tree36dc1bdf810168a3509861fd3a0c61ca562ec272 /Documentation/CodingStyle
parente68e96d2a7b2391cc1f70e207ec9cbe9d092adc9 (diff)
Documentation/CodingStyle: allow multiple return statements per function
A surprising number of newbies interpret this section to mean that only one return statement is allowed per function. Part of the problem is that the "one return statement per function" rule is an actual style guideline that people are used to from other projects. Signed-off-by: Dan Carpenter <> Cc: Eduardo Valentin <> Cc: Rob Landley <> Signed-off-by: Andrew Morton <> Signed-off-by: Linus Torvalds <>
Diffstat (limited to 'Documentation/CodingStyle')
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/CodingStyle b/Documentation/CodingStyle
index e00b8f0dde52..7fe0546c504a 100644
--- a/Documentation/CodingStyle
+++ b/Documentation/CodingStyle
@@ -389,7 +389,8 @@ Albeit deprecated by some people, the equivalent of the goto statement is
used frequently by compilers in form of the unconditional jump instruction.
The goto statement comes in handy when a function exits from multiple
-locations and some common work such as cleanup has to be done.
+locations and some common work such as cleanup has to be done. If there is no
+cleanup needed then just return directly.
The rationale is: