From: Jesper Juhl <juhl-lkml@dif.dk>
To: David Addison <addy@quadrics.com>
Cc: 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: Tue, 26 Apr 2005 18:57:32 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.62.0504261829110.2071@dragon.hyggekrogen.localhost> (raw)
In-Reply-To: <426E62ED.5090803@quadrics.com>
On Tue, 26 Apr 2005, David Addison wrote:
> Hi,
> here is a patch we use to integrate the Quadrics NICs into the Linux kernel.
<snip>
A few small comments below.
>
> +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)
{
body of function
}
<snip>
> +/* ! CONFIG_IOPROC so make all hooks empty */
> +
> +#define ioproc_release(mm) do { } while (0)
> +
> +#define ioproc_sync_range(vma, start, end) do { } while (0)
> +
> +#define ioproc_invalidate_range(vma, start,end) do { } while (0)
> +
> +#define ioproc_update_range(vma, start, end) do { } while (0)
> +
> +#define ioproc_change_protection(vma, start, end, prot) do { } while (0)
> +
> +#define ioproc_sync_page(vma, addr) do { } while (0)
> +
> +#define ioproc_invalidate_page(vma, addr) do { } while (0)
> +
> +#define ioproc_update_page(vma, addr) do { } while (0)
> +
Why all these blank lines between each define? Seems like just a waste of
screen space to me.
--
Jesper Juhl
next prev parent reply other threads:[~2005-04-26 16:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 15:49 David Addison
2005-04-26 16:57 ` Jesper Juhl [this message]
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
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=Pine.LNX.4.62.0504261829110.2071@dragon.hyggekrogen.localhost \
--to=juhl-lkml@dif.dk \
--cc=addy@quadrics.com \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=david.addison@quadrics.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®