linux-kernel - Re: [Ocfs2-devel] [PATCH] ocfs2:Make the function ocfs2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Wed, 24 Jun 2015 08:36:56 +0800
From:	Joseph Qi <joseph.qi@...wei.com>
To:	Nicholas Krause <xerofoify@...il.com>
CC:	<mfasheh@...e.com>, <ocfs2-devel@....oracle.com>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [Ocfs2-devel] [PATCH] ocfs2:Make the function ocfs2_initxattrs
 static

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@...il.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;
> 


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/