From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-mmc@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Wolfram Sang" <wsa+renesas@sang-engineering.com>
Subject: [PATCH 3/3] mmc: sdhi: remove unneeded initialization
Date: Tue, 4 Jun 2019 17:15:30 +0200 [thread overview]
Message-ID: <20190604151530.7023-4-wsa+renesas@sang-engineering.com> (raw)
In-Reply-To: <20190604151530.7023-1-wsa+renesas@sang-engineering.com>
Bools are initialized to 'false' by default.
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
---
drivers/mmc/host/renesas_sdhi_core.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/mmc/host/renesas_sdhi_core.c b/drivers/mmc/host/renesas_sdhi_core.c
index 1cdf5920e861..334fb3527685 100644
--- a/drivers/mmc/host/renesas_sdhi_core.c
+++ b/drivers/mmc/host/renesas_sdhi_core.c
@@ -616,7 +616,6 @@ static const struct renesas_sdhi_quirks sdhi_quirks_4tap_nohs400 = {
};
static const struct renesas_sdhi_quirks sdhi_quirks_4tap = {
- .hs400_disabled = false,
.hs400_4taps = true,
};
--
2.11.0
next prev parent reply other threads:[~2019-06-04 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 15:15 [PATCH 0/3] mmc: sdhi: improve HS400 quirk handling Wolfram Sang
2019-06-04 15:15 ` [PATCH 1/3] mmc: sdhi: disallow HS400 for M3-W ES1.2 and V3H Wolfram Sang
2019-06-04 15:28 ` Geert Uytterhoeven
2019-06-04 15:41 ` Wolfram Sang
2019-06-05 8:31 ` Fabrizio Castro
2019-06-05 8:39 ` Geert Uytterhoeven
2019-06-04 15:15 ` [PATCH 2/3] mmc: sdhi: improve quirk descriptions Wolfram Sang
2019-06-04 15:15 ` Wolfram Sang [this message]
2019-06-10 12:41 ` [PATCH 0/3] mmc: sdhi: improve HS400 quirk handling Niklas Söderlund
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=20190604151530.7023-4-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=yoshihiro.shimoda.uh@renesas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.