linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-fsdevel@vger.kernel.org, cluster-devel@redhat.com,
	akpm <akpm@osdl.org>
Subject: Re: [PATCH -mm] gfs2 lock function parameter
Date: Wed, 29 Nov 2006 08:58:00 +0000	[thread overview]
Message-ID: <1164790680.3752.31.camel@quoit.chygwyn.com> (raw)
In-Reply-To: <20061128222919.89a7ac17.randy.dunlap@oracle.com>

Hi,

I've put this in the -nmw git tree. I'd pull it into the -fixes tree
too, but its probably better to let Linus take whats there first and
then I'll send this on later,

Steve.

On Tue, 2006-11-28 at 22:29 -0800, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
> 
> Fix function parameter typing:
> fs/gfs2/glock.c:100: warning: function declaration isn't a prototype
> 
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> ---
>  fs/gfs2/glock.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> --- linux-2.6.19-rc6-mm2.orig/fs/gfs2/glock.c
> +++ linux-2.6.19-rc6-mm2/fs/gfs2/glock.c
> @@ -96,7 +96,7 @@ static inline rwlock_t *gl_lock_addr(uns
>  	return &gl_hash_locks[x & (GL_HASH_LOCK_SZ-1)];
>  }
>  #else /* not SMP, so no spinlocks required */
> -static inline rwlock_t *gl_lock_addr(x)
> +static inline rwlock_t *gl_lock_addr(unsigned int x)
>  {
>  	return NULL;
>  }
> 
> 
> ---


      reply	other threads:[~2006-11-29  8:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-29  6:29 [PATCH -mm] gfs2 lock function parameter Randy Dunlap
2006-11-29  8:58 ` 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=1164790680.3752.31.camel@quoit.chygwyn.com \
    --to=swhiteho@redhat.com \
    --cc=akpm@osdl.org \
    --cc=cluster-devel@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=randy.dunlap@oracle.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).