From: Frank Li <Frank.li@oss.nxp.com>
To: Ernest Van Hoecke <ernestvanhoecke@gmail.com>
Cc: Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Ernest Van Hoecke <ernest.vanhoecke@toradex.com>
Subject: Re: [PATCH 0/4] arm64: dts: freescale: Add Verdin iMX8M Plus overlays
Date: Thu, 1 Oct 2026 09:29:35 -0500 [thread overview]
Message-ID: <ar5uT0CLf-pVBCve@SMW015318> (raw)
In-Reply-To: <rq5ndq2sqsyoqwhnbdy34etudy4xevdqpm7imgd65uu6gy55nj@wpt6jrgnq2vp>
On Thu, Oct 01, 2026 at 10:25:49AM +0200, Ernest Van Hoecke wrote:
> Hi Frank,
>
> Is there anything blocking this series from being picked up?
I defer all display overlay patches because clock nexus node support
already added.
I hope your ov5460 can move forward. I prefer use this method.
https://lore.kernel.org/imx/20261001-verdin-imx8mp-hmp-camera-ready-v2-0-7d1343ecd3ec@toradex.com/T/#m00174f8e2edb8c6304011e87551b42732e19f428
Frank
>
> Thank you and kind regards,
> Ernest
>
prev parent reply other threads:[~2026-10-01 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 11:41 Ernest Van Hoecke
2026-09-07 11:41 ` [PATCH 1/4] arm64: dts: freescale: imx8mp-verdin: Add NAU8822 Bridge Tied Load Ernest Van Hoecke
2026-09-07 11:41 ` [PATCH 2/4] arm64: dts: freescale: imx8mp-verdin: Add DSI to HDMI adapter overlay Ernest Van Hoecke
2026-09-07 11:41 ` [PATCH 3/4] arm64: dts: freescale: imx8mp-verdin: Add Toradex Capacitive Touch Display 10.1" DSI Ernest Van Hoecke
2026-09-07 11:41 ` [PATCH 4/4] arm64: dts: freescale: imx8mp-verdin: Add Toradex Capacitive Touch Display 7" DSI Ernest Van Hoecke
2026-10-01 8:25 ` [PATCH 0/4] arm64: dts: freescale: Add Verdin iMX8M Plus overlays Ernest Van Hoecke
2026-10-01 14:29 ` Frank Li [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=ar5uT0CLf-pVBCve@SMW015318 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ernest.vanhoecke@toradex.com \
--cc=ernestvanhoecke@gmail.com \
--cc=festevam@gmail.com \
--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 \
/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®