From: Lee Jones <lee@kernel.org>
To: devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Liu Ying <victor.liu@nxp.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, lee@kernel.org,
gregkh@linuxfoundation.org, frank.li@nxp.com
Subject: Re: (subset) [PATCH v2] dt-bindings: mfd: fsl,imx8qxp-csr: Remove binding documentation
Date: Wed, 25 Jun 2025 10:27:12 +0100 [thread overview]
Message-ID: <175084363241.4091583.2132416555571651732.b4-ty@kernel.org> (raw)
In-Reply-To: <20250620022537.3072877-1-victor.liu@nxp.com>
On Fri, 20 Jun 2025 10:25:37 +0800, Liu Ying wrote:
> commit b0a5cde57cf1 ("dt-bindings: mfd: Explain lack of child dependency
> in simple-mfd") pointed out that it's a mistake for a child device of
> a simple MFD device to depend on the simple MFD device's clock resources.
> fsl,imx8qxp-csr.yaml happens to make that mistake. To fix that, remove
> fsl,imx8qxp-csr.yaml and use "simple-pm-bus" and "syscon" as the CSR node's
> compatible strings in the examples of fsl,imx8qxp-pixel-link-msi-bus.yaml
> to replace the wrong compatible strings which include "simple-mfd" and
> "fsl,imx8qxp-mipi-lvds-csr". Since fsl,imx8qxp-pixel-link-msi-bus.yaml
> as the last user of the CSR compatible strings no longer uses them, it's
> safe to remove the fsl,imx8qxp-csr.yaml binding documentation.
>
> [...]
Applied, thanks!
[1/1] dt-bindings: mfd: fsl,imx8qxp-csr: Remove binding documentation
commit: 28c5e6cc6f5d823199798574e2db0ecf22aa6aaa
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2025-06-25 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 2:25 Liu Ying
2025-06-20 14:47 ` Frank Li
2025-06-25 9:27 ` Lee Jones [this message]
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=175084363241.4091583.2132416555571651732.b4-ty@kernel.org \
--to=lee@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frank.li@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=victor.liu@nxp.com \
/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®