From: Rikard Falkeborn <rikard.falkeborn@gmail.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org,
Rikard Falkeborn <rikard.falkeborn@gmail.com>,
support.opensource@diasemi.com,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, patches@opensource.cirrus.com,
Milo Kim <milo.kim@ti.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
Maxime Ripard <mripard@kernel.org>, Chen-Yu Tsai <wens@csie.org>
Subject: [PATCH 0/8] drivers/mfd: Constify static struct resource
Date: Tue, 22 Sep 2020 21:26:51 +0200 [thread overview]
Message-ID: <20200922192659.14535-1-rikard.falkeborn@gmail.com> (raw)
Constify a number of static struct resource to allow the compiler to put
them in read-only memory. Typically, the only usage of these is to assign
their address to the resources field in the mfd_cell struct, which is a
const pointer (a few drivers also read the value of the start field).
I went through the rest of the static instances of struct resource in
drivers/mfd and all of them are either directly modified by the driver
or has its address passed to mfd_add_devices() which takes a non-const
pointer.
The series is compile-tested only.
I split this into patches per maintainer, I'll happily split it (or squash
it) some other way if that's preferable.
Rikard Falkeborn (8):
mfd: da: Constify static struct resource
mfd: intel: Constify static struct resource
mfd: Constify static struct resource in OMAP2+ drivers
mfd: wm: Constify static struct resource
mfd: lp8788: Constify static struct resource
mfd: stmpe: Constify static struct resource
mfd: sun4i-gpadc: Constify static struct resource
mfd: Constify static struct resource
drivers/mfd/88pm800.c | 2 +-
drivers/mfd/88pm860x-core.c | 50 ++++++++++++------------
drivers/mfd/da9055-core.c | 8 ++--
drivers/mfd/da9062-core.c | 24 ++++++------
drivers/mfd/da9063-core.c | 8 ++--
drivers/mfd/da9150-core.c | 6 +--
drivers/mfd/hi655x-pmic.c | 2 +-
drivers/mfd/intel_msic.c | 18 ++++-----
drivers/mfd/intel_quark_i2c_gpio.c | 4 +-
drivers/mfd/intel_soc_pmic_bxtwc.c | 14 +++----
drivers/mfd/intel_soc_pmic_chtdc_ti.c | 10 ++---
drivers/mfd/intel_soc_pmic_chtwc.c | 4 +-
drivers/mfd/intel_soc_pmic_crc.c | 10 ++---
drivers/mfd/ioc3.c | 16 ++++----
drivers/mfd/lp8788.c | 4 +-
drivers/mfd/max8925-core.c | 56 +++++++++++++--------------
drivers/mfd/rdc321x-southbridge.c | 4 +-
drivers/mfd/retu-mfd.c | 4 +-
drivers/mfd/rk808.c | 8 ++--
drivers/mfd/stmpe.c | 10 ++---
drivers/mfd/sun4i-gpadc.c | 2 +-
drivers/mfd/tc3589x.c | 4 +-
drivers/mfd/tc6387xb.c | 2 +-
drivers/mfd/tc6393xb.c | 6 +--
drivers/mfd/tps65090.c | 2 +-
drivers/mfd/tps65217.c | 4 +-
drivers/mfd/tps6586x.c | 2 +-
drivers/mfd/tps65910.c | 2 +-
drivers/mfd/tps80031.c | 2 +-
drivers/mfd/wm831x-core.c | 52 ++++++++++++-------------
drivers/mfd/wm8994-core.c | 4 +-
31 files changed, 172 insertions(+), 172 deletions(-)
--
2.28.0
next reply other threads:[~2020-09-22 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 19:26 Rikard Falkeborn [this message]
2020-09-22 19:26 ` [PATCH 3/8] mfd: Constify static struct resource in OMAP2+ drivers Rikard Falkeborn
2020-11-04 10:57 ` 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=20200922192659.14535-1-rikard.falkeborn@gmail.com \
--to=rikard.falkeborn@gmail.com \
--cc=alexandre.torgue@st.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=milo.kim@ti.com \
--cc=mripard@kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=support.opensource@diasemi.com \
--cc=tony@atomide.com \
--cc=wens@csie.org \
/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