From: Jakob Oestergaard <jakob@unthought.net>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Jesper Juhl <juhl-lkml@dif.dk>, 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
Date: Thu, 28 Apr 2005 13:34:34 +0200 [thread overview]
Message-ID: <20050428113434.GD17359@unthought.net> (raw)
In-Reply-To: <1114535584.5410.2.camel@mindpipe>
On Tue, Apr 26, 2005 at 01:13:04PM -0400, 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.
etags/ctags end of story :)
--
/ jakob
next prev parent reply other threads:[~2005-04-28 11:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 15:49 [PATCH][RFC] Linux VM hooks for advanced RDMA NICs David Addison
2005-04-26 16:57 ` Jesper Juhl
2005-04-26 17:13 ` Lee Revell
2005-04-26 17:20 ` Jesper Juhl
2005-04-26 17:28 ` Lee Revell
2005-04-26 17:38 ` Jesper Juhl
2005-04-26 20:14 ` John W. Linville
2005-04-26 20:17 ` Lee Revell
2005-04-26 20:09 ` Lars Marowsky-Bree
2005-04-28 11:34 ` Jakob Oestergaard [this message]
2005-04-29 8:22 ` Benjamin Herrenschmidt
2005-04-26 17:06 ` Brice Goglin
2005-04-27 9:41 ` David Addison
2005-04-28 8:38 ` Andy Isaacson
2005-04-27 13:43 ` Andi Kleen
2005-04-28 1:42 ` Troy Benjegerdes
2005-04-28 7:21 ` Brice Goglin
2005-04-28 9:21 ` David Addison
2005-04-29 8:19 ` Benjamin Herrenschmidt
2005-04-29 9:25 ` David Addison
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050428113434.GD17359@unthought.net \
--to=jakob@unthought.net \
--cc=addy@quadrics.com \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=david.addison@quadrics.com \
--cc=juhl-lkml@dif.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox