Devicetree
 help / color / mirror / Atom feed
From: Frank.Li@oss.nxp.com
To: 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>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: Frank Li <Frank.Li@nxp.com>,
	Markus Niebel <Markus.Niebel@ew.tq-group.com>,
	imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux@ew.tq-group.com, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v8 1/1] arm64: dts: add tqma9596la-mba95xxca
Date: Thu, 16 Jul 2026 10:49:26 -0400	[thread overview]
Message-ID: <178421335540.3679675.14506765191534970486.b4-ty@b4> (raw)
In-Reply-To: <20260714143154.787825-1-alexander.stein@ew.tq-group.com>

From: Frank Li <Frank.Li@nxp.com>


On Tue, 14 Jul 2026 16:31:52 +0200, Alexander Stein wrote:
> This adds support for TQMa95xxLA modules, designed to be soldered
> on a carrier board. MBa95xxCA is a carrier reference board / starter kit
> design.
> 
> There is a common device tree for all variants with e.g. reduced
> CPU core / feature count.
> 
> [...]

Applied, thanks!

[1/1] arm64: dts: add tqma9596la-mba95xxca
      commit: 4185d10a60d617c5ba7dae4cc56498621c11cd00

Best regards,
-- 
Frank Li <Frank.Li@nxp.com>

      parent reply	other threads:[~2026-07-16 14:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 14:31 [PATCH v8 1/1] arm64: dts: add tqma9596la-mba95xxca Alexander Stein
2026-07-14 15:01 ` sashiko-bot
2026-07-14 15:33   ` Frank Li
2026-07-15  6:45     ` Alexander Stein
2026-07-16 14:49 ` 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=178421335540.3679675.14506765191534970486.b4-ty@b4 \
    --to=frank.li@oss.nxp.com \
    --cc=Frank.Li@nxp.com \
    --cc=Markus.Niebel@ew.tq-group.com \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=geert+renesas@glider.be \
    --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=linux-renesas-soc@vger.kernel.org \
    --cc=linux@ew.tq-group.com \
    --cc=magnus.damm@gmail.com \
    --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