Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Thierry Reding" <thierry.reding@kernel.org>
Cc: mfd@lists.linux.dev, lee@kernel.org, robh@kernel.org,
	devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 3/3] arm64: tegra: Add Tegra132 specific compatible for AHUB
Date: Wed, 30 Sep 2026 14:17:36 +0000	[thread overview]
Message-ID: <20260930141737.6E1FB1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260930-as3722-bindings-v2-3-a3bba649ebf9@nvidia.com>

> From: Thierry Reding <treding@nvidia.com>
> 
> The AHUB on Tegra132 is backwards-compatible with the one found on
> Tegra124, but it needs a specific compatible string anyway, so add
> one.
> 
> Signed-off-by: Thierry Reding <treding@nvidia.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260930-as3722-bindings-v2-0-a3bba649ebf9@nvidia.com?part=3


      reply	other threads:[~2026-09-30 14:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30 14:01 [PATCH v2 0/3] arm64: tegra: Fix DT validation issues for Tegra132 Thierry Reding
2026-09-30 14:01 ` [PATCH v2 1/3] dt-bindings: mfd: as3722: Convert to json-schema Thierry Reding
2026-09-30 14:12   ` sashiko-bot
2026-10-01 19:55   ` Rob Herring (Arm)
2026-09-30 14:01 ` [PATCH v2 2/3] dt-bindings: sound: tegra-ahub: " Thierry Reding
2026-09-30 14:17   ` sashiko-bot
2026-10-01 18:19   ` Mark Brown
2026-10-01 19:56   ` Rob Herring (Arm)
2026-09-30 14:01 ` [PATCH v2 3/3] arm64: tegra: Add Tegra132 specific compatible for AHUB Thierry Reding
2026-09-30 14:17   ` sashiko-bot [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=20260930141737.6E1FB1F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lee@kernel.org \
    --cc=mfd@lists.linux.dev \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=thierry.reding@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