linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: zhengbin <zhengbin13@huawei.com>
To: <ulf.hansson@linaro.org>, <linux-mmc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Cc: <zhengbin13@huawei.com>
Subject: [PATCH 1/6] mmc: core: use true,false for bool variable
Date: Tue, 24 Dec 2019 15:32:10 +0800	[thread overview]
Message-ID: <1577172735-18869-2-git-send-email-zhengbin13@huawei.com> (raw)
In-Reply-To: <1577172735-18869-1-git-send-email-zhengbin13@huawei.com>

Fixes coccicheck warning:

drivers/mmc/core/core.c:60:5-16: WARNING: Assignment of 0/1 to bool variable

Reported-by: Hulk Robot <hulkci@huawei.com>
Signed-off-by: zhengbin <zhengbin13@huawei.com>
---
 drivers/mmc/core/core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/mmc/core/core.c b/drivers/mmc/core/core.c
index abf8f5e..be06320 100644
--- a/drivers/mmc/core/core.c
+++ b/drivers/mmc/core/core.c
@@ -57,7 +57,7 @@ static const unsigned freqs[] = { 400000, 300000, 200000, 100000 };
  * performance cost, and for other reasons may not always be desired.
  * So we allow it it to be disabled.
  */
-bool use_spi_crc = 1;
+bool use_spi_crc = true;
 module_param(use_spi_crc, bool, 0);

 static int mmc_schedule_delayed_work(struct delayed_work *work,
--
2.7.4


  reply	other threads:[~2019-12-24  7:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-24  7:32 [PATCH 0/6] mmc: use true,false for bool variable zhengbin
2019-12-24  7:32 ` zhengbin [this message]
2019-12-24  7:32 ` [PATCH 2/6] mmc: sdhci-tegra: " zhengbin
2019-12-24  7:32 ` [PATCH 3/6] mmc: sdhci-msm: " zhengbin
2019-12-24  7:32 ` [PATCH 4/6] mmc: omap_hsmmc: " zhengbin
2019-12-24  7:32 ` [PATCH 5/6] mmc: davinci: " zhengbin
2019-12-24  7:32 ` [PATCH 6/6] mmc: owl: " zhengbin
2020-01-16 14:39 ` [PATCH 0/6] mmc: " 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=1577172735-18869-2-git-send-email-zhengbin13@huawei.com \
    --to=zhengbin13@huawei.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).