From: Krzysztof Kozlowski <krzk@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Chanwoo Choi <cw00.choi@samsung.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Sangbeom Kim <sbkim73@samsung.com>,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Subject: [PATCH 3/7] regulator: max8660: Constify regulator_ops
Date: Sat, 11 Mar 2017 21:01:20 +0200 [thread overview]
Message-ID: <20170311190124.11512-3-krzk@kernel.org> (raw)
In-Reply-To: <20170311190124.11512-1-krzk@kernel.org>
Static struct regulator_ops (except max8660_dcdc_ops) are not modified
so can be made const for code safeness.
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
---
drivers/regulator/max8660.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/regulator/max8660.c b/drivers/regulator/max8660.c
index b87f62dd484e..a6183425f27d 100644
--- a/drivers/regulator/max8660.c
+++ b/drivers/regulator/max8660.c
@@ -194,7 +194,7 @@ static int max8660_ldo5_set_voltage_sel(struct regulator_dev *rdev,
return max8660_write(max8660, MAX8660_VCC1, 0xff, 0xc0);
}
-static struct regulator_ops max8660_ldo5_ops = {
+static const struct regulator_ops max8660_ldo5_ops = {
.list_voltage = regulator_list_voltage_linear,
.map_voltage = regulator_map_voltage_linear,
.set_voltage_sel = max8660_ldo5_set_voltage_sel,
@@ -252,7 +252,7 @@ static int max8660_ldo67_set_voltage_sel(struct regulator_dev *rdev,
selector << 4);
}
-static struct regulator_ops max8660_ldo67_ops = {
+static const struct regulator_ops max8660_ldo67_ops = {
.is_enabled = max8660_ldo67_is_enabled,
.enable = max8660_ldo67_enable,
.disable = max8660_ldo67_disable,
--
2.9.3
next prev parent reply other threads:[~2017-03-11 19:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170311190141epcas2p2721283aa79819ca89f11815414ae5b4a@epcas2p2.samsung.com>
2017-03-11 19:01 ` [PATCH 1/7] regulator: max1586: Constify regulator_ops Krzysztof Kozlowski
2017-03-11 19:01 ` [PATCH 2/7] regulator: max77693: " Krzysztof Kozlowski
2017-03-13 4:55 ` Chanwoo Choi
2017-03-13 16:56 ` Applied "regulator: max77693: Constify regulator_ops" to the regulator tree Mark Brown
2017-03-11 19:01 ` Krzysztof Kozlowski [this message]
2017-03-13 16:56 ` Applied "regulator: max8660: " Mark Brown
2017-03-11 19:01 ` [PATCH 4/7] regulator: s2mpa01: Constify regulator_ops Krzysztof Kozlowski
2017-03-13 16:56 ` Applied "regulator: s2mpa01: Constify regulator_ops" to the regulator tree Mark Brown
2017-03-11 19:01 ` [PATCH 5/7] regulator: s2mps11: Constify regulator_ops Krzysztof Kozlowski
2017-03-13 16:56 ` Applied "regulator: s2mps11: Constify regulator_ops" to the regulator tree Mark Brown
2017-03-11 19:01 ` [PATCH 6/7] regulator: s5m8767: Constify regulator_ops Krzysztof Kozlowski
2017-03-13 16:56 ` Applied "regulator: s5m8767: Constify regulator_ops" to the regulator tree Mark Brown
2017-03-11 19:01 ` [PATCH 7/7] regulator: s2mpa01: Fix inconsistent indenting Krzysztof Kozlowski
2017-03-13 16:56 ` Applied "regulator: s2mpa01: Fix inconsistent indenting" to the regulator tree Mark Brown
2017-03-13 5:00 ` [PATCH 1/7] regulator: max1586: Constify regulator_ops Chanwoo Choi
2017-03-13 16:56 ` Applied "regulator: max1586: Constify regulator_ops" to the regulator tree 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=20170311190124.11512-3-krzk@kernel.org \
--to=krzk@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=sbkim73@samsung.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).