From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [2.6 patch] fs/dlm/user.c should #include "user.h"
Date: Mon, 26 Feb 2007 10:13:28 +0000 [thread overview]
Message-ID: <1172484808.11001.594.camel@quoit.chygwyn.com> (raw)
In-Reply-To: <20070225231842.GD29575@stusta.de>
Hi,
Now applied to the git tree. Thanks,
Steve.
On Mon, 2007-02-26 at 00:18 +0100, Adrian Bunk wrote:
> Every file should include the headers containing the prototypes for
> it's global functions.
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
>
> ---
> --- linux-2.6.20-mm2/fs/dlm/user.c.old 2007-02-25 19:40:16.000000000 +0100
> +++ linux-2.6.20-mm2/fs/dlm/user.c 2007-02-25 19:40:29.000000000 +0100
> @@ -22,6 +22,7 @@
> #include "lockspace.h"
> #include "lock.h"
> #include "lvb_table.h"
> +#include "user.h"
>
> static const char *name_prefix="dlm";
> static struct miscdevice ctl_device;
>
prev parent reply other threads:[~2007-02-26 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 23:18 [Cluster-devel] [2.6 patch] fs/dlm/user.c should #include "user.h" Adrian Bunk
2007-02-26 10:13 ` Steven Whitehouse [this message]
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=1172484808.11001.594.camel@quoit.chygwyn.com \
--to=swhiteho@redhat.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;
as well as URLs for NNTP newsgroup(s).