From: kbuild test robot <fengguang.wu@intel.com>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: kbuild-all@01.org, linux-mmc@vger.kernel.org,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: [ulf.hansson-mmc:next 27/28] drivers/mmc/core/block.c:2106:9-10: WARNING: return of 0/1 in function 'mmc_blk_status_error' with return type bool
Date: Thu, 30 Nov 2017 05:54:24 +0800 [thread overview]
Message-ID: <201711300522.IoizUSEn%fengguang.wu@intel.com> (raw)
tree: git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git next
head: 98f67755cf2dc07fc0d79c534deb28634b58e391
commit: 89eb3e6b5f77fe3d5579adc13f75d610487e03c3 [27/28] mmc: block: blk-mq: Stop using legacy recovery
coccinelle warnings: (new ones prefixed by >>)
>> drivers/mmc/core/block.c:2106:9-10: WARNING: return of 0/1 in function 'mmc_blk_status_error' with return type bool
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next reply other threads:[~2017-11-29 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 21:54 kbuild test robot [this message]
2017-11-29 21:54 ` [PATCH] mmc: block: blk-mq: fix boolreturn.cocci warnings kbuild test robot
2017-11-30 12:02 ` Adrian Hunter
2017-11-30 13:09 ` Ulf Hansson
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=201711300522.IoizUSEn%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=adrian.hunter@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.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