From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Mark Brown <broonie@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: linux-kernel@vger.kernel.org, "Thomas Weißschuh" <linux@weissschuh.net>
Subject: [PATCH 1/2] const_structs.checkpatch: add regmap structs
Date: Sat, 06 Jul 2024 13:13:41 +0200 [thread overview]
Message-ID: <20240706-regmap-const-structs-v1-1-d08c776da787@weissschuh.net> (raw)
In-Reply-To: <20240706-regmap-const-structs-v1-0-d08c776da787@weissschuh.net>
Many structs used by regmap should be const by default.
Add entries to const_structs.checkpatch for them for checkpatch.pl to
warn on new non-const additions.
Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
---
scripts/const_structs.checkpatch | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/scripts/const_structs.checkpatch b/scripts/const_structs.checkpatch
index 52e5bfb61fd0..1bfbb3d7f2e0 100644
--- a/scripts/const_structs.checkpatch
+++ b/scripts/const_structs.checkpatch
@@ -64,7 +64,16 @@ platform_suspend_ops
proc_ops
proto_ops
pwm_ops
+reg_default
+reg_field
+reg_sequence
regmap_access_table
+regmap_bus
+regmap_config
+regmap_irq
+regmap_irq_chip
+regmap_range
+regmap_range_cfg
regulator_ops
reset_control_ops
rpc_pipe_ops
--
2.45.2
next prev parent reply other threads:[~2024-07-06 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-06 11:13 [PATCH 0/2] regmap: add const_struct.checkpatch entries and constify regmap_irq_sub_irq_map Thomas Weißschuh
2024-07-06 11:13 ` Thomas Weißschuh [this message]
2024-07-06 11:13 ` [PATCH 2/2] regmap-irq: handle const struct regmap_irq_sub_irq_map Thomas Weißschuh
2024-07-08 14:26 ` [PATCH 0/2] regmap: add const_struct.checkpatch entries and constify regmap_irq_sub_irq_map 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=20240706-regmap-const-structs-v1-1-d08c776da787@weissschuh.net \
--to=linux@weissschuh.net \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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
all inboxes | Powered by JetHome®