Date: Tue, 26 Apr 2005 19:20:13 +0200 (CEST)
From: Jesper Juhl <juhl-lkml@dif.dk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: David Addison <addy@quadrics.com>, linux-kernel@vger.kernel.org,
       Andrew Morton <akpm@osdl.org>, Andrea Arcangeli <andrea@suse.de>,
       David Addison <david.addison@quadrics.com>
Subject: Re: [PATCH][RFC] Linux VM hooks for advanced RDMA NICs
In-Reply-To: <1114535584.5410.2.camel@mindpipe>
Message-ID: <Pine.LNX.4.62.0504261918210.2071@dragon.hyggekrogen.localhost>
References: <426E62ED.5090803@quadrics.com> 
 <Pine.LNX.4.62.0504261829110.2071@dragon.hyggekrogen.localhost>
 <1114535584.5410.2.camel@mindpipe>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1130
Lines: 33

On Tue, 26 Apr 2005, Lee Revell wrote:

> On Tue, 2005-04-26 at 18:57 +0200, Jesper Juhl wrote:
> > > 
> > > +static inline void
> > > +ioproc_release(struct mm_struct *mm)
> > > +{
> > 
> > Return types on same line as function name makes grep'ing a lot 
> > easier/nicer.
> > 
> > Here's the example from Documentation/CodingStyle : 
> > 
> >         int function(int x)
> >         {
> 
> How so?  I never understood the reasons.  This makes it easier to grep
> for everything that returns int.  But you make the common case (what
> file is function() defined in?) harder.
> 
I don't know what you do, but when I'm grep'ing the tree for some function 
I'm often looking for its return type, having that on the same line as the 
function name lets me grep for the function name and the grep output will 
contain the return type and function name nicely on the same line.

-- 
Jesper

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/