From: sashiko-bot@kernel.org
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: imx@lists.linux.dev, linux-gpio@vger.kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH v2 7/9] gpio: mxc: use local dev variable
Date: Mon, 05 Oct 2026 14:34:28 +0000 [thread overview]
Message-ID: <20261005143428.6F3601F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261005-gpio-mxc-cleanup-v2-7-bdc3afbb35e2@nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] gpio: mxc: implicit inclusion of linux/of.h
--
commit 28b12eaf4d41de364ce05354d1c3c8a369023e5d
Author: Peng Fan <peng.fan@nxp.com>
gpio: mxc: use local dev variable
This commit introduces a local dev variable to replace repeated &pdev->dev
dereferences in mxc_gpio_probe() to improve readability. It also switches
to the device-model device_is_compatible() API while retaining the np
variable for of_alias_get_id().
> diff --git a/drivers/gpio/gpio-mxc.c b/drivers/gpio/gpio-mxc.c
> index c92331f192f91..d762d03c8d6a3 100644
> --- a/drivers/gpio/gpio-mxc.c
> +++ b/drivers/gpio/gpio-mxc.c
> @@ -24,7 +24,7 @@
> #include <linux/syscore_ops.h>
> #include <linux/gpio/driver.h>
> #include <linux/gpio/generic.h>
> -#include <linux/of.h>
> +#include <linux/property.h>
> #include <linux/bug.h>
[Severity: Low]
Does removing the linux/of.h inclusion violate the 'include what you use'
(IWYU) principle?
Looking at mxc_gpio_probe(), the code still explicitly relies on
of_alias_get_id() when CONFIG_GPIO_SYSFS is enabled:
if (IS_ENABLED(CONFIG_GPIO_SYSFS))
port->gen_gc.gc.base = of_alias_get_id(np, "gpio") * 32;
While this compiles today because linux/of.h happens to be implicitly
included through other headers, could removing the explicit include cause
future build breakages if those internal include chains change?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261005-gpio-mxc-cleanup-v2-0-bdc3afbb35e2@nxp.com?part=7
next prev parent reply other threads:[~2026-10-05 14:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 14:21 [PATCH v2 0/9] gpio: mxc: bug fixes and probe cleanup Peng Fan (OSS)
2026-10-05 14:21 ` [PATCH v2 1/9] gpio: mxc: fix race between chained IRQ handler install and probe completion Peng Fan (OSS)
2026-10-05 14:21 ` [PATCH v2 2/9] gpio: mxc: fix wakeup_pads bit operations Peng Fan (OSS)
2026-10-06 8:36 ` Andy Shevchenko
2026-10-06 12:52 ` Peng Fan
2026-10-05 14:21 ` [PATCH v2 3/9] gpio: mxc: replace of_device_is_compatible() with hwdata flags Peng Fan (OSS)
2026-10-05 14:21 ` [PATCH v2 4/9] gpio: mxc: convert pad wakeup compatible checks to " Peng Fan (OSS)
2026-10-05 14:21 ` [PATCH v2 5/9] gpio: mxc: convert probe error handling to devres Peng Fan (OSS)
2026-10-05 14:34 ` sashiko-bot
2026-10-05 14:21 ` [PATCH v2 6/9] gpio: mxc: switch probe error paths to dev_err_probe() Peng Fan (OSS)
2026-10-05 14:21 ` [PATCH v2 7/9] gpio: mxc: use local dev variable Peng Fan (OSS)
2026-10-05 14:34 ` sashiko-bot [this message]
2026-10-05 14:21 ` [PATCH v2 8/9] gpio: mxc: introduce MXC_ICR macros and use field_prep/field_get Peng Fan (OSS)
2026-10-05 14:21 ` [PATCH v2 9/9] gpio: mxc: use BIT() macro for single-bit operations Peng Fan (OSS)
2026-10-06 10:16 ` Linus Walleij
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=20261005143428.6F3601F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=imx@lists.linux.dev \
--cc=linux-gpio@vger.kernel.org \
--cc=peng.fan@oss.nxp.com \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.