public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: fengguang.wu@intel.com
Cc: Steven Whitehouse <swhiteho@redhat.com>,
	cluster-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH linux-gfs2] GFS2: ht_parms can be static
Date: Tue, 14 Jul 2015 09:39:36 -0400 (EDT)	[thread overview]
Message-ID: <342310271.38145368.1436881176059.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20150713201750.GA103147@roam>

----- Original Message -----
> 
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
> ---
>  glock.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/gfs2/glock.c b/fs/gfs2/glock.c
> index 813de00..1b0dff4 100644
> --- a/fs/gfs2/glock.c
> +++ b/fs/gfs2/glock.c
> @@ -76,7 +76,7 @@ static DEFINE_SPINLOCK(lru_lock);
>  #define GFS2_GL_HASH_SHIFT      15
>  #define GFS2_GL_HASH_SIZE       (1 << GFS2_GL_HASH_SHIFT)
>  
> -struct rhashtable_params ht_parms = {
> +static struct rhashtable_params ht_parms = {
>  	.nelem_hint = GFS2_GL_HASH_SIZE * 3 / 4,
>  	.key_len = sizeof(struct lm_lockname),
>  	.key_offset = offsetof(struct gfs2_glock, gl_name),
> 

Hi,

Thanks. Now pushed to the for-next branch of the linux-gfs2 tree.

Regards,

Bob Peterson
Red Hat File Systems

      reply	other threads:[~2015-07-14 13:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13 20:17 [linux-gfs2:for-next 2/2] fs/gfs2/glock.c:79:26: sparse: symbol 'ht_parms' was not declared. Should it be static? kbuild test robot
2015-07-13 20:17 ` [PATCH linux-gfs2] GFS2: ht_parms can be static kbuild test robot
2015-07-14 13:39   ` Bob Peterson [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=342310271.38145368.1436881176059.JavaMail.zimbra@redhat.com \
    --to=rpeterso@redhat.com \
    --cc=cluster-devel@redhat.com \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=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