cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [2.6 patch] gfs2/ops_file.c should #include "ops_inode.h"
Date: Mon, 18 Feb 2008 11:15:24 +0000	[thread overview]
Message-ID: <1203333324.9635.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20080217081712.GF3848@cs181133002.pp.htv.fi>

Hi,

Now in the GFS2 -nmw git tree. Thanks,

Steve.

On Sun, 2008-02-17 at 10:17 +0200, Adrian Bunk wrote:
> Every file should include the headers containing the prototypes for
> its global functions (in this case for gfs2_set_inode_flags()).
> 
> Signed-off-by: Adrian Bunk <bunk@kernel.org>
> 
> ---
> 34f925ebad8d18c4061536e275e33e888f827fd6 diff --git a/fs/gfs2/ops_file.c b/fs/gfs2/ops_file.c
> index f4842f2..64fd81c 100644
> --- a/fs/gfs2/ops_file.c
> +++ b/fs/gfs2/ops_file.c
> @@ -39,6 +39,7 @@
>  #include "util.h"
>  #include "eaops.h"
>  #include "ops_address.h"
> +#include "ops_inode.h"
>  
>  /**
>   * gfs2_llseek - seek to a location in a file
> 



      reply	other threads:[~2008-02-18 11:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-17  8:17 [Cluster-devel] [2.6 patch] gfs2/ops_file.c should #include "ops_inode.h" Adrian Bunk
2008-02-18 11:15 ` 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=1203333324.9635.3.camel@localhost.localdomain \
    --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).