From: Steven French <sfrench@samba.org>
To: Yang Li <yang.lee@linux.alibaba.com>,
David Howells <dhowells@redhat.com>
Cc: linux-cifs@vger.kernel.org, samba-technical@lists.samba.org,
linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH -next] cifs: Return true/false (not 1/0) from bool functions
Date: Sun, 22 May 2022 16:09:10 -0500 [thread overview]
Message-ID: <679693c4-8c4c-85b0-e4f2-7f34be3bad12@samba.org> (raw)
In-Reply-To: <20220504130634.101239-1-yang.lee@linux.alibaba.com>
Do you remember which patch caused this? Perhaps one of Dave Howell's
iov_iter cifs patches that was temporarily in for-next? I don't see it
anymore
On 5/4/22 08:06, Yang Li wrote:
> Return boolean values ("true" or "false") instead of 1 or 0 from bool
> functions. This fixes the following warnings from coccicheck:
>
> ./fs/cifs/file.c:4764:9-10: WARNING: return of 0/1 in function
> cifs_release_folio() with return type bool
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
> ---
> fs/cifs/file.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/cifs/file.c b/fs/cifs/file.c
> index 580a847aa8b5..a9123cefd84f 100644
> --- a/fs/cifs/file.c
> +++ b/fs/cifs/file.c
> @@ -4761,7 +4761,7 @@ static int cifs_write_begin(struct file *file, struct address_space *mapping,
> static bool cifs_release_folio(struct folio *folio, gfp_t gfp)
> {
> if (folio_test_private(folio))
> - return 0;
> + return false;
> if (folio_test_fscache(folio)) {
> if (current_is_kswapd() || !(gfp & __GFP_FS))
> return false;
prev parent reply other threads:[~2022-05-22 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 13:06 [PATCH -next] cifs: Return true/false (not 1/0) from bool functions Yang Li
2022-05-22 21:09 ` Steven French [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=679693c4-8c4c-85b0-e4f2-7f34be3bad12@samba.org \
--to=sfrench@samba.org \
--cc=abaci@linux.alibaba.com \
--cc=dhowells@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=yang.lee@linux.alibaba.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