From: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Support Opensource <support.opensource@diasemi.com>,
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-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: [PATCH 12/12] regulator: sy8106a: Fix W=1 build warning when CONFIG_OF=n
Date: Thu, 20 Aug 2020 15:47:04 +0800 [thread overview]
Message-ID: <20200820154704.14554720@xhacker.debian> (raw)
In-Reply-To: <20200820152926.42c48840@xhacker.debian>
Fix below warning when CONFIG_OF=n:
drivers/regulator/sy8106a-regulator.c:126:34: warning: ‘sy8106a_i2c_of_match’ defined but not used [-Wunused-const-variable=]
126 | static const struct of_device_id sy8106a_i2c_of_match[] = {
| ^~~~~~~~~~~~~~~~~~~~
Signed-off-by: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
---
drivers/regulator/sy8106a-regulator.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/regulator/sy8106a-regulator.c b/drivers/regulator/sy8106a-regulator.c
index 2222e739e62b..1878caf4dd40 100644
--- a/drivers/regulator/sy8106a-regulator.c
+++ b/drivers/regulator/sy8106a-regulator.c
@@ -123,11 +123,13 @@ static int sy8106a_i2c_probe(struct i2c_client *i2c)
return 0;
}
+#ifdef CONFIG_OF
static const struct of_device_id sy8106a_i2c_of_match[] = {
{ .compatible = "silergy,sy8106a" },
{ },
};
MODULE_DEVICE_TABLE(of, sy8106a_i2c_of_match);
+#endif
static const struct i2c_device_id sy8106a_i2c_id[] = {
{ "sy8106a", 0 },
--
2.28.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Support Opensource <support.opensource@diasemi.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Icenowy Zheng <icenowy@aosc.io>
Cc: linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 12/12] regulator: sy8106a: Fix W=1 build warning when CONFIG_OF=n
Date: Thu, 20 Aug 2020 15:47:04 +0800 [thread overview]
Message-ID: <20200820154704.14554720@xhacker.debian> (raw)
In-Reply-To: <20200820152926.42c48840@xhacker.debian>
Fix below warning when CONFIG_OF=n:
drivers/regulator/sy8106a-regulator.c:126:34: warning: ‘sy8106a_i2c_of_match’ defined but not used [-Wunused-const-variable=]
126 | static const struct of_device_id sy8106a_i2c_of_match[] = {
| ^~~~~~~~~~~~~~~~~~~~
Signed-off-by: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
---
drivers/regulator/sy8106a-regulator.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/regulator/sy8106a-regulator.c b/drivers/regulator/sy8106a-regulator.c
index 2222e739e62b..1878caf4dd40 100644
--- a/drivers/regulator/sy8106a-regulator.c
+++ b/drivers/regulator/sy8106a-regulator.c
@@ -123,11 +123,13 @@ static int sy8106a_i2c_probe(struct i2c_client *i2c)
return 0;
}
+#ifdef CONFIG_OF
static const struct of_device_id sy8106a_i2c_of_match[] = {
{ .compatible = "silergy,sy8106a" },
{ },
};
MODULE_DEVICE_TABLE(of, sy8106a_i2c_of_match);
+#endif
static const struct i2c_device_id sy8106a_i2c_id[] = {
{ "sy8106a", 0 },
--
2.28.0
next prev parent reply other threads:[~2020-08-20 7:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200820152926.42c48840@xhacker.debian>
2020-08-20 7:32 ` [PATCH 01/12] regulator: 88pg86x: Fix W=1 build warning when CONFIG_OF=n Jisheng Zhang
2020-08-20 7:32 ` Jisheng Zhang
2020-08-20 7:33 ` [PATCH 02/12] regulator: da9210: " Jisheng Zhang
2020-08-20 7:33 ` Jisheng Zhang
2020-08-20 7:34 ` [PATCH 03/12] regulator: fan53555: " Jisheng Zhang
2020-08-20 7:34 ` Jisheng Zhang
2020-08-20 7:34 ` [PATCH 04/12] regulator: fixed: Fix W=1 build warnings " Jisheng Zhang
2020-08-20 7:34 ` Jisheng Zhang
2020-08-20 7:35 ` [PATCH 05/12] regulator: ltc3589: Fix W=1 build warning " Jisheng Zhang
2020-08-20 7:35 ` Jisheng Zhang
2020-08-20 7:36 ` [PATCH 06/12] regulator: ltc3676: " Jisheng Zhang
2020-08-20 7:36 ` Jisheng Zhang
2020-08-20 7:37 ` [PATCH 07/12] regulator: max1586: " Jisheng Zhang
2020-08-20 7:37 ` Jisheng Zhang
2020-08-20 7:37 ` [PATCH 08/12] regulator: max77826: " Jisheng Zhang
2020-08-20 7:37 ` Jisheng Zhang
2020-08-20 7:38 ` [PATCH 09/12] regulator: pwm: " Jisheng Zhang
2020-08-20 7:38 ` Jisheng Zhang
2020-08-20 7:46 ` [PATCH 11/12] regulator: stm32-vrefbuf: " Jisheng Zhang
2020-08-20 7:46 ` Jisheng Zhang
2020-08-20 8:13 ` Fabrice Gasnier
2020-08-20 8:13 ` Fabrice Gasnier
2020-08-20 8:32 ` Jisheng Zhang
2020-08-20 8:32 ` Jisheng Zhang
2020-08-20 10:51 ` Mark Brown
2020-08-20 10:51 ` Mark Brown
2020-08-20 7:47 ` Jisheng Zhang [this message]
2020-08-20 7:47 ` [PATCH 12/12] regulator: sy8106a: " Jisheng Zhang
2020-08-20 8:00 ` [PATCH 10/12] regulator: stm32-pwr: " Jisheng Zhang
2020-08-20 8:00 ` Jisheng Zhang
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=20200820154704.14554720@xhacker.debian \
--to=jisheng.zhang@synaptics.com \
--cc=alexandre.torgue@st.com \
--cc=broonie@kernel.org \
--cc=icenowy@aosc.io \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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 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.