From: Shawn Guo <shawn.gsc@gmail.com>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Marek Vasut <marex@denx.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>, Li Yang <leoyang.li@nxp.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/4] TQMa8Xx (i.MX8QXP/i.MX8DXP) support
Date: Thu, 1 Feb 2024 17:47:48 +0800 [thread overview]
Message-ID: <20240201094748.GC463595@dragon> (raw)
In-Reply-To: <20231214142327.1962914-1-alexander.stein@ew.tq-group.com>
On Thu, Dec 14, 2023 at 03:23:23PM +0100, Alexander Stein wrote:
> Alexander Stein (4):
> arm64: dts: imx: add imx8dxp support
> dt-bindings: arm: add TQMa8Xx boards
> arm64: dts: freescale: add initial device tree for TQMa8Xx
> arm64: defconfig: Enable i.MX8QXP device drivers
Applied all, thanks!
prev parent reply other threads:[~2024-02-01 1:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 14:23 [PATCH v2 0/4] TQMa8Xx (i.MX8QXP/i.MX8DXP) support Alexander Stein
2023-12-14 14:23 ` [PATCH v2 1/4] arm64: dts: imx: add imx8dxp support Alexander Stein
2023-12-14 14:23 ` [PATCH v2 2/4] dt-bindings: arm: add TQMa8Xx boards Alexander Stein
2023-12-14 14:23 ` [PATCH v2 3/4] arm64: dts: freescale: add initial device tree for TQMa8Xx Alexander Stein
2023-12-14 14:23 ` [PATCH v2 4/4] arm64: defconfig: Enable i.MX8QXP device drivers Alexander Stein
2024-02-01 9:47 ` 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=20240201094748.GC463595@dragon \
--to=shawn.gsc@gmail.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=will@kernel.org \
/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).