From: Shawn Guo <shawnguo2@yeah.net>
To: Frank Li <Frank.Li@nxp.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shengjiu Wang <shengjiu.wang@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/4] arm: dts: nxp: imx6: fix esai related dtb_check warning
Date: Thu, 25 Apr 2024 14:04:13 +0800 [thread overview]
Message-ID: <ZinyXZ6NhhX1ETlI@dragon> (raw)
In-Reply-To: <20240416-esai_arm_dts_warning-v2-0-879e59c0c3b8@nxp.com>
On Tue, Apr 16, 2024 at 10:47:46AM -0400, Frank Li wrote:
> Frank Li (4):
...
> arm: dts: nxp: imx6sx: fix esai related warning when do dtb_check
> arm: dts: nxp: imx6qdl: fix esai clock warning when do dtb_check
We historically use prefix "ARM: dts: ..." for i.MX arm DTS changes.
Fixed them up and applied.
Shawn
prev parent reply other threads:[~2024-04-25 6:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 14:47 [PATCH v2 0/4] arm: dts: nxp: imx6: fix esai related dtb_check warning Frank Li
2024-04-16 14:47 ` [PATCH v2 1/4] ASoC: dt-bindings: fsl-esai: Remove 'fsl,*' from required list Frank Li
2024-04-16 14:47 ` [PATCH v2 2/4] ASoC: dt-bindings: fsl-esai: Add ref: dai-common.yaml Frank Li
2024-04-16 14:47 ` [PATCH v2 3/4] arm: dts: nxp: imx6sx: fix esai related warning when do dtb_check Frank Li
2024-04-16 14:47 ` [PATCH v2 4/4] arm: dts: nxp: imx6qdl: fix esai clock " Frank Li
2024-04-17 2:46 ` (subset) [PATCH v2 0/4] arm: dts: nxp: imx6: fix esai related dtb_check warning Mark Brown
2024-04-25 6:04 ` Shawn Guo [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=ZinyXZ6NhhX1ETlI@dragon \
--to=shawnguo2@yeah.net \
--cc=Frank.Li@nxp.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=shengjiu.wang@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).