Devicetree
 help / color / mirror / Atom feed
From: Sumit Gupta <sumitg@nvidia.com>
To: treding@nvidia.com, jonathanh@nvidia.com, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: bbasu@nvidia.com, sumitg@nvidia.com
Subject: Re: [PATCH 0/3] arm64: dts: tegra: CPU and cache node updates
Date: Mon, 22 Jun 2026 16:14:13 +0530	[thread overview]
Message-ID: <d89e306f-0947-4bfa-843d-664ee3139dfb@nvidia.com> (raw)
In-Reply-To: <20260121104536.3214101-1-sumitg@nvidia.com>


On 21/01/26 16:15, Sumit Gupta wrote:
> - Fixes for Tegra234/264 device tree CPU compatible string.
> - Populate CPU and L2 cache nodes for Tegra264.
>
> Sumit Gupta (3):
>    arm64: dts: tegra234: Fix CPU compatible string to cortex-a78ae
>    arm64: dts: tegra264: Fix CPU1 node unit-address
>    arm64: dts: tegra264: Populate CPU and L2 cache nodes
>
>   arch/arm64/boot/dts/nvidia/tegra234.dtsi |  24 +-
>   arch/arm64/boot/dts/nvidia/tegra264.dtsi | 323 ++++++++++++++++++++++-
>   2 files changed, 334 insertions(+), 13 deletions(-)
>

A gentle reminder on this series, which got missed and is pending.

I have verified it still applies cleanly on top of linux-next.
Please take a look when you get a chance.

Thanks,
Sumit



  parent reply	other threads:[~2026-06-22 10:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-21 10:45 [PATCH 0/3] arm64: dts: tegra: CPU and cache node updates Sumit Gupta
2026-01-21 10:45 ` [PATCH 1/3] arm64: dts: tegra234: Fix CPU compatible string to cortex-a78ae Sumit Gupta
2026-01-21 10:45 ` [PATCH 2/3] arm64: dts: tegra264: Fix CPU1 node unit-address Sumit Gupta
2026-01-21 10:45 ` [PATCH 3/3] arm64: dts: tegra264: Populate CPU and L2 cache nodes Sumit Gupta
2026-06-22 10:44 ` Sumit Gupta [this message]
2026-06-25  9:10 ` [PATCH 0/3] arm64: dts: tegra: CPU and cache node updates Thierry Reding

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=d89e306f-0947-4bfa-843d-664ee3139dfb@nvidia.com \
    --to=sumitg@nvidia.com \
    --cc=bbasu@nvidia.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=treding@nvidia.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