From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Samuel Ortiz <sameo@linux.intel.com>, Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org, Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH -v2 01/10] mfd: dialog: Constify struct mfd_cell where possible
Date: Mon, 18 Nov 2013 14:32:57 +0100 [thread overview]
Message-ID: <1384781586-4798-1-git-send-email-geert@linux-m68k.org> (raw)
As of commit 03e361b25ee8dfb1fd9b890072c23c4aae01c6c7 ("mfd: Stop setting
refcounting pointers in original mfd_cell arrays"), the "cell" parameter of
mfd_add_devices() is "const" again. Hence make all cell data passed to
mfd_add_devices() const where possible.
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
---
v2: Split in groups
drivers/mfd/da9052-core.c | 2 +-
drivers/mfd/da9055-core.c | 2 +-
drivers/mfd/da9063-core.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/mfd/da9052-core.c b/drivers/mfd/da9052-core.c
index ea28a33576e4..25838f10b35b 100644
--- a/drivers/mfd/da9052-core.c
+++ b/drivers/mfd/da9052-core.c
@@ -427,7 +427,7 @@ int da9052_adc_read_temp(struct da9052 *da9052)
}
EXPORT_SYMBOL_GPL(da9052_adc_read_temp);
-static struct mfd_cell da9052_subdev_info[] = {
+static const struct mfd_cell da9052_subdev_info[] = {
{
.name = "da9052-regulator",
.id = 1,
diff --git a/drivers/mfd/da9055-core.c b/drivers/mfd/da9055-core.c
index d3670cd3c3c6..caf8dcffd0ad 100644
--- a/drivers/mfd/da9055-core.c
+++ b/drivers/mfd/da9055-core.c
@@ -294,7 +294,7 @@ static struct resource da9055_ld05_6_resource = {
.flags = IORESOURCE_IRQ,
};
-static struct mfd_cell da9055_devs[] = {
+static const struct mfd_cell da9055_devs[] = {
{
.of_compatible = "dialog,da9055-gpio",
.name = "da9055-gpio",
diff --git a/drivers/mfd/da9063-core.c b/drivers/mfd/da9063-core.c
index c9cf8d988406..26937cd01071 100644
--- a/drivers/mfd/da9063-core.c
+++ b/drivers/mfd/da9063-core.c
@@ -75,7 +75,7 @@ static struct resource da9063_hwmon_resources[] = {
};
-static struct mfd_cell da9063_devs[] = {
+static const struct mfd_cell da9063_devs[] = {
{
.name = DA9063_DRVNAME_REGULATORS,
.num_resources = ARRAY_SIZE(da9063_regulators_resources),
--
1.7.9.5
next reply other threads:[~2013-11-18 13:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 13:32 Geert Uytterhoeven [this message]
2013-11-18 13:32 ` [PATCH -v2 02/10] mfd: intel: Constify struct mfd_cell where possible Geert Uytterhoeven
2013-11-18 13:32 ` [PATCH -v2 03/10] mfd: marvell: " Geert Uytterhoeven
2013-11-18 13:33 ` [PATCH -v2 04/10] mfd: maxim: " Geert Uytterhoeven
2013-11-18 13:33 ` [PATCH -v2 05/10] mfd: stmicro: " Geert Uytterhoeven
2013-11-18 13:33 ` [PATCH -v2 06/10] mfd: ti: " Geert Uytterhoeven
2013-11-18 13:33 ` [PATCH -v2 07/10] mfd: toshiba: " Geert Uytterhoeven
2013-11-18 13:33 ` [PATCH -v2 08/10] mfd: wolfson: " Geert Uytterhoeven
2013-11-18 13:33 ` [PATCH -v2 09/10] mfd: staging: " Geert Uytterhoeven
2013-11-21 11:02 ` Lee Jones
2013-11-21 15:16 ` Greg Kroah-Hartman
2013-11-18 13:33 ` [PATCH -v2 10/10] mfd: " Geert Uytterhoeven
2013-11-18 14:29 ` [PATCH -v2 01/10] mfd: dialog: " Lee Jones
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=1384781586-4798-1-git-send-email-geert@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.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).