From: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Support Opensource <support.opensource@diasemi.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Icenowy Zheng <icenowy@aosc.io>
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 03/15] regulator: fan53555: Fix W=1 build warning when CONFIG_OF=n
Date: Fri, 21 Aug 2020 11:13:24 +0800 [thread overview]
Message-ID: <20200821111324.430fe1da@xhacker.debian> (raw)
In-Reply-To: <20200821111135.0b958d3a@xhacker.debian>
Fix below warning when CONFIG_OF=n:
drivers/regulator/fan53555.c:439:34: warning: ‘fan53555_dt_ids’ defined but not used [-Wunused-const-variable=]
439 | static const struct of_device_id fan53555_dt_ids[] = {
| ^~~~~~~~~~~~~~~
Signed-off-by: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
---
drivers/regulator/fan53555.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/fan53555.c b/drivers/regulator/fan53555.c
index 00c83492f774..aa426183b6a1 100644
--- a/drivers/regulator/fan53555.c
+++ b/drivers/regulator/fan53555.c
@@ -436,7 +436,7 @@ static struct fan53555_platform_data *fan53555_parse_dt(struct device *dev,
return pdata;
}
-static const struct of_device_id fan53555_dt_ids[] = {
+static const struct of_device_id __maybe_unused fan53555_dt_ids[] = {
{
.compatible = "fcs,fan53526",
.data = (void *)FAN53526_VENDOR_FAIRCHILD,
--
2.28.0
next prev parent reply other threads:[~2020-08-21 3:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 3:11 [PATCH v2 00/15] regulator: Fix W=1 build warning when CONFIG_OF=n Jisheng Zhang
2020-08-21 3:12 ` [PATCH v2 01/15] regulator: 88pg86x: " Jisheng Zhang
2020-08-21 3:12 ` [PATCH v2 02/15] regulator: da9210: " Jisheng Zhang
2020-08-21 8:56 ` Adam Thomson
2020-08-21 3:13 ` Jisheng Zhang [this message]
2020-08-21 3:14 ` [PATCH v2 04/15] regulator: fixed: Fix W=1 build warnings " Jisheng Zhang
2020-08-21 3:14 ` [PATCH v2 05/15] regulator: ltc3589: Fix W=1 build warning " Jisheng Zhang
2020-08-21 3:15 ` [PATCH v2 06/15] regulator: ltc3676: " Jisheng Zhang
2020-08-21 3:16 ` [PATCH v2 07/15] regulator: max1586: " Jisheng Zhang
2020-08-21 3:16 ` [PATCH v2 08/15] regulator: max77826: " Jisheng Zhang
2020-08-21 3:16 ` [PATCH v2 09/15] regulator: pwm: " Jisheng Zhang
2020-08-21 3:17 ` [PATCH v2 10/15] regulator: stm32-pwr: " Jisheng Zhang
2020-08-21 3:17 ` [PATCH v2 11/15] regulator: stm32-vrefbuf: " Jisheng Zhang
2020-08-21 8:05 ` Fabrice Gasnier
2020-08-21 3:18 ` [PATCH v2 12/15] regulator: sy8106a: " Jisheng Zhang
2020-08-21 3:19 ` [PATCH v2 13/15] regulator: qcom-rpmh: " Jisheng Zhang
2020-08-21 3:19 ` [PATCH v2 14/15] regulator: stm32-booster: " Jisheng Zhang
2020-08-21 8:06 ` Fabrice Gasnier
2020-08-21 3:20 ` [PATCH v2 15/15] regulator: tps65023: " Jisheng Zhang
2020-08-21 16:40 ` [PATCH v2 00/15] regulator: " Mark Brown
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=20200821111324.430fe1da@xhacker.debian \
--to=jisheng.zhang@synaptics.com \
--cc=agross@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=icenowy@aosc.io \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=support.opensource@diasemi.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).