linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: Zheng Bin <zhengbin13@huawei.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2] fuse: use true,false for bool variable
Date: Thu, 6 Feb 2020 13:10:48 +0100	[thread overview]
Message-ID: <CAJfpegvibrehmHd6d+Kb6FGv6wS8iybGi+QdnnSW-iNMfQV2BQ@mail.gmail.com> (raw)
In-Reply-To: <1579005585-20249-1-git-send-email-zhengbin13@huawei.com>

On Tue, Jan 14, 2020 at 1:32 PM Zheng Bin <zhengbin13@huawei.com> wrote:
>
> From: zhengbin <zhengbin13@huawei.com>
>
> Fixes coccicheck warning:
>
> fs/fuse/readdir.c:335:1-19: WARNING: Assignment of 0/1 to bool variable
> fs/fuse/file.c:1398:2-19: WARNING: Assignment of 0/1 to bool variable
> fs/fuse/file.c:1400:2-20: WARNING: Assignment of 0/1 to bool variable
> fs/fuse/cuse.c:454:1-20: WARNING: Assignment of 0/1 to bool variable
> fs/fuse/cuse.c:455:1-19: WARNING: Assignment of 0/1 to bool variable
> fs/fuse/inode.c:497:2-17: WARNING: Assignment of 0/1 to bool variable
> fs/fuse/inode.c:504:2-23: WARNING: Assignment of 0/1 to bool variable
> fs/fuse/inode.c:511:2-22: WARNING: Assignment of 0/1 to bool variable
> fs/fuse/inode.c:518:2-23: WARNING: Assignment of 0/1 to bool variable
> fs/fuse/inode.c:522:2-26: WARNING: Assignment of 0/1 to bool variable
> fs/fuse/inode.c:526:2-18: WARNING: Assignment of 0/1 to bool variable
> fs/fuse/inode.c:1000:1-20: WARNING: Assignment of 0/1 to bool variable
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: zhengbin <zhengbin13@huawei.com>

Thanks, applied.

Miklos

      reply	other threads:[~2020-02-06 12:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 12:39 [PATCH v2] fuse: use true,false for bool variable Zheng Bin
2020-02-06 12:10 ` Miklos Szeredi [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=CAJfpegvibrehmHd6d+Kb6FGv6wS8iybGi+QdnnSW-iNMfQV2BQ@mail.gmail.com \
    --to=miklos@szeredi.hu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=zhengbin13@huawei.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;
as well as URLs for NNTP newsgroup(s).