All of lore.kernel.org
 help / color / mirror / Atom feed
* [merged] documentation-codingstyle-allow-multiple-return-statements-per-function.patch removed from -mm tree
@ 2013-07-08 19:35 akpm
  0 siblings, 0 replies; only message in thread
From: akpm @ 2013-07-08 19:35 UTC (permalink / raw)
  To: mm-commits, rob, eduardo.valentin, dan.carpenter

Subject: [merged] documentation-codingstyle-allow-multiple-return-statements-per-function.patch removed from -mm tree
To: dan.carpenter@oracle.com,eduardo.valentin@ti.com,rob@landley.net,mm-commits@vger.kernel.org
From: akpm@linux-foundation.org
Date: Mon, 08 Jul 2013 12:35:33 -0700


The patch titled
     Subject: Documentation/CodingStyle: allow multiple return statements per function
has been removed from the -mm tree.  Its filename was
     documentation-codingstyle-allow-multiple-return-statements-per-function.patch

This patch was dropped because it was merged into mainline or a subsystem tree

------------------------------------------------------
From: Dan Carpenter <dan.carpenter@oracle.com>
Subject: 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 <dan.carpenter@oracle.com>
Cc: Eduardo Valentin <eduardo.valentin@ti.com>
Cc: Rob Landley <rob@landley.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 Documentation/CodingStyle |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff -puN Documentation/CodingStyle~documentation-codingstyle-allow-multiple-return-statements-per-function Documentation/CodingStyle
--- a/Documentation/CodingStyle~documentation-codingstyle-allow-multiple-return-statements-per-function
+++ a/Documentation/CodingStyle
@@ -389,7 +389,8 @@ Albeit deprecated by some people, the eq
 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:
 
_

Patches currently in -mm which might be from dan.carpenter@oracle.com are

origin.patch
linux-next.patch
fanotify-info-leak-in-copy_event_to_user.patch
fs-convert-fs-shrinkers-to-new-scan-count-api-fix-fix.patch
mm-vmallocc-unbreak-__vunmap.patch
mwave-fix-info-leak-in-mwave_ioctl.patch
lib-scatterlist-error-handling-in-__sg_alloc_table.patch


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2013-07-08 19:35 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-07-08 19:35 [merged] documentation-codingstyle-allow-multiple-return-statements-per-function.patch removed from -mm tree akpm

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.