linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
	linux-fsdevel@vger.kernel.org
Cc: kbuild-all@lists.01.org, viro@zeniv.linux.org.uk,
	linux-kernel@vger.kernel.org, pali@kernel.org, dsterba@suse.cz,
	aaptel@suse.com, willy@infradead.org, rdunlap@infradead.org,
	joe@perches.com, mark@harmstone.com
Subject: [PATCH] fs/ntfs3: fix boolreturn.cocci warnings
Date: Sun, 28 Mar 2021 10:13:32 +0800	[thread overview]
Message-ID: <20210328021332.GA68309@116d7529a87d> (raw)
In-Reply-To: <20210327214023.3214923-10-almaz.alexandrovich@paragon-software.com>

From: kernel test robot <lkp@intel.com>

fs/ntfs3/xattr.c:1037:8-9: WARNING: return of 0/1 in function 'ntfs_xattr_user_list' with return type bool

 Return statements in functions returning bool should use
 true/false instead of 1/0.
Generated by: scripts/coccinelle/misc/boolreturn.cocci

CC: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---

url:    https://github.com/0day-ci/linux/commits/Konstantin-Komarov/NTFS-read-write-driver-GPL-implementation-by-Paragon-Software/20210328-054516
base:   931294922e65a23e1aad6398b9ae02df74044679

 xattr.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/fs/ntfs3/xattr.c
+++ b/fs/ntfs3/xattr.c
@@ -1034,7 +1034,7 @@ out:
 
 static bool ntfs_xattr_user_list(struct dentry *dentry)
 {
-	return 1;
+	return true;
 }
 
 static const struct xattr_handler ntfs_xattr_handler = {

  parent reply	other threads:[~2021-03-28  2:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-27 21:40 [PATCH v25 00/10] NTFS read-write driver GPL implementation by Paragon Software Konstantin Komarov
2021-03-27 21:40 ` [PATCH v25 01/10] fs/ntfs3: Add headers and misc files Konstantin Komarov
2021-03-27 21:40 ` [PATCH v25 02/10] fs/ntfs3: Add initialization of super block Konstantin Komarov
2021-03-27 21:40 ` [PATCH v25 03/10] fs/ntfs3: Add bitmap Konstantin Komarov
2021-03-27 21:40 ` [PATCH v25 04/10] fs/ntfs3: Add file operations and implementation Konstantin Komarov
2021-03-27 21:40 ` [PATCH v25 05/10] fs/ntfs3: Add attrib operations Konstantin Komarov
2021-03-27 21:40 ` [PATCH v25 06/10] fs/ntfs3: Add compression Konstantin Komarov
2021-03-27 21:40 ` [PATCH v25 07/10] fs/ntfs3: Add NTFS journal Konstantin Komarov
2021-03-27 21:40 ` [PATCH v25 08/10] fs/ntfs3: Add Kconfig, Makefile and doc Konstantin Komarov
2021-03-27 21:40 ` [PATCH v25 09/10] fs/ntfs3: Add NTFS3 in fs/Kconfig and fs/Makefile Konstantin Komarov
2021-03-28  2:13   ` kernel test robot
2021-03-28  2:13   ` kernel test robot [this message]
2021-03-28  2:13   ` [PATCH] fs/ntfs3: fix d_find_alias.cocci warnings kernel test robot
2021-03-27 21:40 ` [PATCH v25 10/10] fs/ntfs3: Add MAINTAINERS Konstantin Komarov

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=20210328021332.GA68309@116d7529a87d \
    --to=lkp@intel.com \
    --cc=aaptel@suse.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=dsterba@suse.cz \
    --cc=joe@perches.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@harmstone.com \
    --cc=pali@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.org \
    /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).