From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Andy Whitcroft <apw@canonical.com>,
Joe Perches <joe@perches.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Fabio Estevam <festevam@gmail.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>
Cc: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
Haibo Chen <haibo.chen@nxp.com>,
Catalin Popescu <catalin.popescu@leica-geosystems.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 2/4] checkpatch: warn about use of legacy_static_base
Date: Mon, 13 Jan 2025 23:19:10 +0100 [thread overview]
Message-ID: <20250113-b4-imx-gpio-base-warning-v1-2-0a28731a5cf6@pengutronix.de> (raw)
In-Reply-To: <20250113-b4-imx-gpio-base-warning-v1-0-0a28731a5cf6@pengutronix.de>
gpio_chip::legacy_state_base was recently added as opt-out for
existing drivers and shouldn't be used for new drivers. It's thus
sensible to add a deprecation warning whenever it's used.
This doesn't fit with the existing deprecated API check, because it
requires a `(' to follow the symbol name, so a new member specific
pattern is introduced instead.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
scripts/checkpatch.pl | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 7b28ad3317427a6bf9e27b77065aa3915cb13053..6c57a08833a4298573c7967b2a178fd7f46aa7ce 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -848,6 +848,13 @@ foreach my $entry (keys %deprecated_apis) {
}
$deprecated_apis_search = "(?:${deprecated_apis_search})";
+our %deprecated_members = (
+ "legacy_static_base" => "setting .base to -1",
+);
+
+our $deprecated_memb_search = "(?:" . join("|", keys %deprecated_members) . ")";
+%deprecated_apis = (%deprecated_apis, %deprecated_members);
+
our $mode_perms_world_writable = qr{
S_IWUGO |
S_IWOTH |
@@ -7407,8 +7414,8 @@ sub process {
}
# check for deprecated apis
- if ($line =~ /\b($deprecated_apis_search)\b\s*\(/) {
- my $deprecated_api = $1;
+ if ($line =~ /\b(?<old>$deprecated_apis_search)\b\s*\(|(?:->|\.)(?<old>$deprecated_memb_search)\b/) {
+ my $deprecated_api = ${^CAPTURE}{old};
my $new_api = $deprecated_apis{$deprecated_api};
WARN("DEPRECATED_API",
"Deprecated use of '$deprecated_api', prefer '$new_api' instead\n" . $herecurr);
--
2.39.5
next prev parent reply other threads:[~2025-01-13 22:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 22:19 [PATCH 0/4] gpio: mxc: silence warning about GPIO base being statically allocated Ahmad Fatoum
2025-01-13 22:19 ` [PATCH 1/4] gpiolib: add opt-out for existing drivers with static GPIO base Ahmad Fatoum
2025-01-14 9:49 ` Andy Shevchenko
2025-01-14 10:06 ` Ahmad Fatoum
2025-01-14 19:38 ` Andy Shevchenko
2025-01-15 7:07 ` Ahmad Fatoum
2025-01-15 13:04 ` Kent Gibson
2025-01-21 10:26 ` Ahmad Fatoum
2025-01-15 12:00 ` Linus Walleij
2025-01-21 11:34 ` Ahmad Fatoum
2025-01-13 22:19 ` Ahmad Fatoum [this message]
2025-01-14 14:37 ` [PATCH 2/4] checkpatch: warn about use of legacy_static_base Linus Walleij
2025-01-13 22:19 ` [PATCH 3/4] gpio: mxc: remove dead code after switch to DT-only Ahmad Fatoum
2025-01-14 9:51 ` Andy Shevchenko
2025-01-15 16:55 ` Bartosz Golaszewski
2025-01-21 10:16 ` Ahmad Fatoum
2025-01-13 22:19 ` [PATCH 4/4] gpio: mxc: silence warning about GPIO base being statically allocated Ahmad Fatoum
2025-01-14 9:46 ` [PATCH 0/4] " Andy Shevchenko
2025-01-14 9:55 ` Ahmad Fatoum
2025-01-14 19:43 ` Andy Shevchenko
2025-01-15 7:03 ` Ahmad Fatoum
2025-01-15 15:16 ` Andy Shevchenko
2025-01-21 11:16 ` Ahmad Fatoum
2025-01-15 16:52 ` Bartosz Golaszewski
2025-01-21 10:37 ` Ahmad Fatoum
2025-01-23 9:19 ` Bartosz Golaszewski
2025-01-23 8:06 ` (subset) " Bartosz Golaszewski
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=20250113-b4-imx-gpio-base-warning-v1-2-0a28731a5cf6@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=andy.shevchenko@gmail.com \
--cc=apw@canonical.com \
--cc=brgl@bgdev.pl \
--cc=catalin.popescu@leica-geosystems.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=dwaipayanray1@gmail.com \
--cc=festevam@gmail.com \
--cc=haibo.chen@nxp.com \
--cc=imx@lists.linux.dev \
--cc=joe@perches.com \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).