From: Javier Carrasco <javier.carrasco.cruz@gmail.com>
To: Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Eric Tremblay <etremblay@distech-controls.com>,
Robert Marko <robert.marko@sartura.hr>,
Luka Perkov <luka.perkov@sartura.hr>
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
Javier Carrasco <javier.carrasco.cruz@gmail.com>
Subject: [PATCH 0/3] hwmon: constify struct regmap_config
Date: Tue, 02 Jul 2024 12:09:29 +0200 [thread overview]
Message-ID: <20240702-hwmon-const-regmap-v1-0-63f6d4765fe0@gmail.com> (raw)
This series adds the const modifier to the remaining regmap_config
structs within the hwmon subsystem that are effectively used as const
(i.e., only read after their declaration), but kept ad writtable data.
Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
---
Javier Carrasco (3):
hwmon: (ina238) Constify struct regmap_config
hwmon: (tmp513) Constify struct regmap_config
hwmon: (tps23861) Constify struct regmap_config
drivers/hwmon/ina238.c | 2 +-
drivers/hwmon/tmp513.c | 2 +-
drivers/hwmon/tps23861.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
---
base-commit: 39b24cced70fdc336dbc0070f8b3bde61d8513a8
change-id: 20240702-hwmon-const-regmap-4d4e3c097d9e
Best regards,
--
Javier Carrasco <javier.carrasco.cruz@gmail.com>
next reply other threads:[~2024-07-02 10:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 10:09 Javier Carrasco [this message]
2024-07-02 10:09 ` [PATCH 1/3] hwmon: (ina238) Constify struct regmap_config Javier Carrasco
2024-07-02 18:30 ` Guenter Roeck
2024-07-02 10:09 ` [PATCH 2/3] hwmon: (tmp513) " Javier Carrasco
2024-07-02 18:31 ` Guenter Roeck
2024-07-02 10:09 ` [PATCH 3/3] hwmon: (tps23861) " Javier Carrasco
2024-07-02 18:31 ` Guenter Roeck
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=20240702-hwmon-const-regmap-v1-0-63f6d4765fe0@gmail.com \
--to=javier.carrasco.cruz@gmail.com \
--cc=etremblay@distech-controls.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=luka.perkov@sartura.hr \
--cc=robert.marko@sartura.hr \
/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