From: Shawn Guo <shawnguo@kernel.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: aisheng.dong@nxp.com, devicetree@vger.kernel.org,
festevam@gmail.com, han.xu@nxp.com, imx@lists.linux.dev,
kernel@pengutronix.de, krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org, linux-imx@nxp.com,
linux-kernel@vger.kernel.org, peng.fan@nxp.com,
robh+dt@kernel.org, s.hauer@pengutronix.de, shenwei.wang@nxp.com
Subject: Re: [PATCH v2 0/6] add adc0 flexspi lpspi to 8dxl evk board dts
Date: Mon, 14 Nov 2022 16:49:13 +0800 [thread overview]
Message-ID: <20221114084913.GU2649582@dragon> (raw)
In-Reply-To: <20221111154742.2753318-1-Frank.Li@nxp.com>
On Fri, Nov 11, 2022 at 10:47:36AM -0500, Frank Li wrote:
> Add adc0 flexspi lpspi and adc to 8dxl evk board dts
>
> Change from v1 to v2:
> split SOC and board change to two patches.
>
> Frank Li (6):
> arm64: dts: imx8dxl: add adc0 support
> arm64: dts: imx8dxl_evk: add adc0 support
> arm64: dts: imx8dxl: add flexspi0 support
> arm64: dts: imx8dxl_evk: add flexspi0 support
> arm64: dts: imx8dxl: add lpspi support
> arm64: dts: imx8dxl_evk: add lpspi0 support
Applied all, thanks!
prev parent reply other threads:[~2022-11-14 8:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 15:47 [PATCH v2 0/6] add adc0 flexspi lpspi to 8dxl evk board dts Frank Li
2022-11-11 15:47 ` [PATCH v2 1/6] arm64: dts: imx8dxl: add adc0 support Frank Li
2022-11-11 15:47 ` [PATCH v2 2/6] arm64: dts: imx8dxl_evk: " Frank Li
2022-11-11 15:47 ` [PATCH v2 3/6] arm64: dts: imx8dxl: add flexspi0 support Frank Li
2022-11-11 15:47 ` [PATCH v2 4/6] arm64: dts: imx8dxl_evk: " Frank Li
2022-11-11 15:47 ` [PATCH v2 5/6] arm64: dts: imx8dxl: add lpspi support Frank Li
2022-11-11 15:47 ` [PATCH v2 6/6] arm64: dts: imx8dxl_evk: add lpspi0 support Frank Li
2022-11-14 8:49 ` 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=20221114084913.GU2649582@dragon \
--to=shawnguo@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=han.xu@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shenwei.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 NNTP newsgroup(s).