From: sashiko-bot@kernel.org
To: "Lakshay Piplani" <lakshay.piplani@nxp.com>
Cc: linux-i3c@lists.infradead.org,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org,
mfd@lists.linux.dev, lee@kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH v20 5/8] regulator: p3h2x4x: Add driver for on-die regulators in NXP P3H2x4x i3c hub
Date: Tue, 22 Sep 2026 10:47:25 +0000 [thread overview]
Message-ID: <20260922104726.6A9121F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260922103551.2754613-6-lakshay.piplani@nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] mfd: driver-specific header placed in global include directory
--
commit 51d204aed0d51828d1e68a0ac0a10f8c8cac311b
Author: Aman Kumar Pandey <aman.kumarpandey@nxp.com>
regulator: p3h2x4x: Add driver for on-die regulators in NXP P3H2x4x i3c hub
This commit adds a regulator driver for the on-die regulators in the NXP
P3H2x4x i3c hub device, registering them via the regulator subsystem using
the MFD framework.
> diff --git a/drivers/regulator/p3h2840_i3c_hub_regulator.c b/drivers/regulator/p3h2840_i3c_hub_regulator.c
> new file mode 100644
> index 0000000000000..244f2a4f70f38
> --- /dev/null
> +++ b/drivers/regulator/p3h2840_i3c_hub_regulator.c
> @@ -0,0 +1,289 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Copyright 2025-2026 NXP
> + * NXP P3H2X4X regulator driver file contain functions for enable/disable regulator
> + * and voltage set/get.
> + */
> +#include <linux/bitfield.h>
> +#include <linux/cleanup.h>
> +#include <linux/mfd/p3h2840.h>
[Severity: Low]
Does this include violate the MFD subsystem guidelines for driver-specific
headers?
The MFD guidelines state that driver-specific header files used only by the
parent and its immediate children should be kept local to drivers/mfd/
rather than being placed in the global include/linux/mfd/ directory. Since
this header appears to only be used by the p3h2840 parent and children,
could it be moved to the local subsystem directory to avoid polluting the
global include space?
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260922103551.2754613-1-lakshay.piplani@nxp.com?part=5
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Lakshay Piplani" <lakshay.piplani@nxp.com>
Cc: linux-i3c@lists.infradead.org,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org,
mfd@lists.linux.dev, lee@kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH v20 5/8] regulator: p3h2x4x: Add driver for on-die regulators in NXP P3H2x4x i3c hub
Date: Tue, 22 Sep 2026 10:47:25 +0000 [thread overview]
Message-ID: <20260922104726.6A9121F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260922103551.2754613-6-lakshay.piplani@nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] mfd: driver-specific header placed in global include directory
--
commit 51d204aed0d51828d1e68a0ac0a10f8c8cac311b
Author: Aman Kumar Pandey <aman.kumarpandey@nxp.com>
regulator: p3h2x4x: Add driver for on-die regulators in NXP P3H2x4x i3c hub
This commit adds a regulator driver for the on-die regulators in the NXP
P3H2x4x i3c hub device, registering them via the regulator subsystem using
the MFD framework.
> diff --git a/drivers/regulator/p3h2840_i3c_hub_regulator.c b/drivers/regulator/p3h2840_i3c_hub_regulator.c
> new file mode 100644
> index 0000000000000..244f2a4f70f38
> --- /dev/null
> +++ b/drivers/regulator/p3h2840_i3c_hub_regulator.c
> @@ -0,0 +1,289 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Copyright 2025-2026 NXP
> + * NXP P3H2X4X regulator driver file contain functions for enable/disable regulator
> + * and voltage set/get.
> + */
> +#include <linux/bitfield.h>
> +#include <linux/cleanup.h>
> +#include <linux/mfd/p3h2840.h>
[Severity: Low]
Does this include violate the MFD subsystem guidelines for driver-specific
headers?
The MFD guidelines state that driver-specific header files used only by the
parent and its immediate children should be kept local to drivers/mfd/
rather than being placed in the global include/linux/mfd/ directory. Since
this header appears to only be used by the p3h2840 parent and children,
could it be moved to the local subsystem directory to avoid polluting the
global include space?
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260922103551.2754613-1-lakshay.piplani@nxp.com?part=5
next prev parent reply other threads:[~2026-09-22 10:47 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 10:35 [PATCH v20 0/8] Add support for NXP P3H2x4x I3C hub driver Lakshay Piplani
2026-09-22 10:35 ` Lakshay Piplani
2026-09-22 10:35 ` [PATCH v20 1/8] i3c: master: Add APIs for I3C hub support Lakshay Piplani
2026-09-22 10:35 ` Lakshay Piplani
2026-09-22 10:48 ` sashiko-bot
2026-09-22 10:48 ` sashiko-bot
2026-09-22 10:35 ` [PATCH v20 2/8] i3c: master: Add controller-only device operation helpers Lakshay Piplani
2026-09-22 10:35 ` Lakshay Piplani
2026-09-22 10:45 ` sashiko-bot
2026-09-22 10:45 ` sashiko-bot
2026-09-22 10:35 ` [PATCH v20 3/8] dt-bindings: i3c: Add NXP P3H2x4x i3c-hub support Lakshay Piplani
2026-09-22 10:35 ` Lakshay Piplani
2026-09-22 10:44 ` sashiko-bot
2026-09-22 10:44 ` sashiko-bot
2026-09-22 10:35 ` [PATCH v20 4/8] mfd: p3h2x4x: Add driver for NXP P3H2x4x i3c hub and on-die regulator Lakshay Piplani
2026-09-22 10:35 ` Lakshay Piplani
2026-09-22 10:50 ` sashiko-bot
2026-09-22 10:50 ` sashiko-bot
2026-09-22 10:35 ` [PATCH v20 5/8] regulator: p3h2x4x: Add driver for on-die regulators in NXP P3H2x4x i3c hub Lakshay Piplani
2026-09-22 10:35 ` Lakshay Piplani
2026-09-22 10:47 ` sashiko-bot [this message]
2026-09-22 10:47 ` sashiko-bot
2026-09-22 10:35 ` [PATCH v20 6/8] i3c: hub: Add support for the I3C interface in the I3C hub Lakshay Piplani
2026-09-22 10:35 ` Lakshay Piplani
2026-09-22 10:53 ` sashiko-bot
2026-09-22 10:53 ` sashiko-bot
2026-09-22 10:35 ` [PATCH v20 7/8] i3c: hub: p3h2x4x: Add support for NXP P3H2x4x I3C hub functionality Lakshay Piplani
2026-09-22 10:35 ` Lakshay Piplani
2026-09-22 10:55 ` sashiko-bot
2026-09-22 10:55 ` sashiko-bot
2026-09-22 10:35 ` [PATCH v20 8/8] i3c: hub: p3h2x4x: Add SMBus slave mode support Lakshay Piplani
2026-09-22 10:35 ` Lakshay Piplani
2026-09-22 10:55 ` sashiko-bot
2026-09-22 10:55 ` sashiko-bot
2026-09-30 14:23 ` (subset) [PATCH v20 0/8] Add support for NXP P3H2x4x I3C hub driver Alexandre Belloni
2026-09-30 14:23 ` Alexandre Belloni
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=20260922104726.6A9121F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lakshay.piplani@nxp.com \
--cc=lee@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=mfd@lists.linux.dev \
--cc=robh@kernel.org \
--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.