From: Julia Lawall <Julia.Lawall@lip6.fr>
To: linux-rpi-kernel@lists.infradead.org
Cc: bhumirks@gmail.com, kernel-janitors@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, linux-input@vger.kernel.org,
linux-hwmon@vger.kernel.org
Subject: [PATCH 0/9 v2] constify thermal_zone_of_device_ops structures
Date: Tue, 8 Aug 2017 17:08:54 +0200 [thread overview]
Message-ID: <1502204943-20075-1-git-send-email-Julia.Lawall@lip6.fr> (raw)
The thermal_zone_of_device_ops structures are only passed as the fourth
argument to thermal_zone_of_sensor_register or
devm_thermal_zone_of_sensor_register, both of which are declared as const.
Thus the thermal_zone_of_device_ops structures themselves can be const.
v2: add structures passed to devm_thermal_zone_of_sensor_register also.
Done with the help of Coccinelle.
---
drivers/hwmon/hwmon.c | 2 +-
drivers/hwmon/scpi-hwmon.c | 2 +-
drivers/input/touchscreen/sun4i-ts.c | 2 +-
drivers/thermal/broadcom/bcm2835_thermal.c | 2 +-
drivers/thermal/hisi_thermal.c | 2 +-
drivers/thermal/qoriq_thermal.c | 2 +-
drivers/thermal/rcar_gen3_thermal.c | 2 +-
drivers/thermal/samsung/exynos_tmu.c | 2 +-
drivers/thermal/zx2967_thermal.c | 2 +-
9 files changed, 9 insertions(+), 9 deletions(-)
next reply other threads:[~2017-08-08 15:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 15:08 Julia Lawall [this message]
2017-08-08 15:08 ` [PATCH 1/9 v2] thermal: hisilicon: constify thermal_zone_of_device_ops structures Julia Lawall
2017-08-08 15:08 ` [PATCH 2/9 v2] thermal: qoriq: " Julia Lawall
2017-08-08 15:08 ` [PATCH 3/9 v2] thermal: rcar_gen3_thermal: " Julia Lawall
2017-08-08 15:08 ` [PATCH 4/9 v2] thermal: zx2967: " Julia Lawall
2017-08-08 15:08 ` [PATCH 5/9 v2] thermal: exynos: " Julia Lawall
2017-08-08 15:09 ` [PATCH 7/9 v2] thermal: bcm2835: " Julia Lawall
2017-08-08 19:58 ` Stefan Wahren
2017-08-11 3:36 ` [PATCH 0/9 v2] " Zhang Rui
2017-08-11 5:17 ` Julia Lawall
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=1502204943-20075-1-git-send-email-Julia.Lawall@lip6.fr \
--to=julia.lawall@lip6.fr \
--cc=bhumirks@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.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