All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Qi <joseph.qi@huawei.com>
To: Nicholas Krause <xerofoify@gmail.com>
Cc: mfasheh@suse.com, ocfs2-devel@oss.oracle.com,
	linux-kernel@vger.kernel.org
Subject: [Ocfs2-devel] [PATCH] ocfs2:Make the function ocfs2_initxattrs static
Date: Wed, 24 Jun 2015 08:36:56 +0800	[thread overview]
Message-ID: <5589FBA8.7020204@huawei.com> (raw)
In-Reply-To: <1435103331-16407-1-git-send-email-xerofoify@gmail.com>

Hi Nicholas,
It has already been staged as a part of the patch "ocfs2: mark local
functions as static" in the -mm tree.
Thanks all the same.

--
Joseph

On 2015/6/24 7:48, Nicholas Krause wrote:
> This makes the function ocfs2_initxattrs static now due
> to this function's only caller being in its own declaration
> and definition file of xattr.c.
> 
> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
> ---
>  fs/ocfs2/xattr.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/ocfs2/xattr.c b/fs/ocfs2/xattr.c
> index d03bfbf..889f379 100644
> --- a/fs/ocfs2/xattr.c
> +++ b/fs/ocfs2/xattr.c
> @@ -7271,7 +7271,7 @@ static int ocfs2_xattr_security_set(struct dentry *dentry, const char *name,
>  			       name, value, size, flags);
>  }
>  
> -int ocfs2_initxattrs(struct inode *inode, const struct xattr *xattr_array,
> +static int ocfs2_initxattrs(struct inode *inode, const struct xattr *xattr_array,
>  		     void *fs_info)
>  {
>  	const struct xattr *xattr;
> 

WARNING: multiple messages have this Message-ID (diff)
From: Joseph Qi <joseph.qi@huawei.com>
To: Nicholas Krause <xerofoify@gmail.com>
Cc: <mfasheh@suse.com>, <ocfs2-devel@oss.oracle.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [Ocfs2-devel] [PATCH] ocfs2:Make the function ocfs2_initxattrs static
Date: Wed, 24 Jun 2015 08:36:56 +0800	[thread overview]
Message-ID: <5589FBA8.7020204@huawei.com> (raw)
In-Reply-To: <1435103331-16407-1-git-send-email-xerofoify@gmail.com>

Hi Nicholas,
It has already been staged as a part of the patch "ocfs2: mark local
functions as static" in the -mm tree.
Thanks all the same.

--
Joseph

On 2015/6/24 7:48, Nicholas Krause wrote:
> This makes the function ocfs2_initxattrs static now due
> to this function's only caller being in its own declaration
> and definition file of xattr.c.
> 
> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
> ---
>  fs/ocfs2/xattr.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/ocfs2/xattr.c b/fs/ocfs2/xattr.c
> index d03bfbf..889f379 100644
> --- a/fs/ocfs2/xattr.c
> +++ b/fs/ocfs2/xattr.c
> @@ -7271,7 +7271,7 @@ static int ocfs2_xattr_security_set(struct dentry *dentry, const char *name,
>  			       name, value, size, flags);
>  }
>  
> -int ocfs2_initxattrs(struct inode *inode, const struct xattr *xattr_array,
> +static int ocfs2_initxattrs(struct inode *inode, const struct xattr *xattr_array,
>  		     void *fs_info)
>  {
>  	const struct xattr *xattr;
> 



  reply	other threads:[~2015-06-24  0:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23 23:48 [Ocfs2-devel] [PATCH] ocfs2:Make the function ocfs2_initxattrs static Nicholas Krause
2015-06-24  0:36 ` Joseph Qi [this message]
2015-06-24  0:36   ` Joseph Qi

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=5589FBA8.7020204@huawei.com \
    --to=joseph.qi@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfasheh@suse.com \
    --cc=ocfs2-devel@oss.oracle.com \
    --cc=xerofoify@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.