[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAFLxGvzW=Z3Lk==NXS159DF4WUJqzAELS_E++ruKDVio_hfo4A@mail.gmail.com>
Date: Wed, 15 May 2019 23:06:02 +0200
From: Richard Weinberger <richard.weinberger@...il.com>
To: Vandana BN <bnvandana@...il.com>
Cc: Richard Weinberger <richard@....at>,
Artem Bityutskiy <dedekind1@...il.com>,
Adrian Hunter <adrian.hunter@...el.com>,
linux-mtd@...ts.infradead.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] fs: ubifs: Resolve sparse warning for using plain integer
as NULL pointer
On Mon, May 6, 2019 at 11:24 PM Vandana BN <bnvandana@...il.com> wrote:
>
> fs/ubifs/xattr.c:615:58: warning: Using plain integer as NULL pointer
>
> Signed-off-by: Vandana BN <bnvandana@...il.com>
> ---
> fs/ubifs/xattr.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ubifs/xattr.c b/fs/ubifs/xattr.c
> index f5ad1ede7990..066a5666c50f 100644
> --- a/fs/ubifs/xattr.c
> +++ b/fs/ubifs/xattr.c
> @@ -612,7 +612,7 @@ int ubifs_init_security(struct inode *dentry, struct inode *inode,
> int err;
>
> err = security_inode_init_security(inode, dentry, qstr,
> - &init_xattrs, 0);
> + &init_xattrs, NULL);
> if (err) {
> struct ubifs_info *c = dentry->i_sb->s_fs_info;
> ubifs_err(c, "cannot initialize security for inode %lu, error %d",
> --
> 2.17.1
Applied.
--
Thanks,
//richard
Powered by blists - more mailing lists