From: Rob Herring <robh@kernel.org>
To: Thierry Reding <thierry.reding@kernel.org>
Cc: Lee Jones <lee@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Laxman Dewangan <ldewangan@nvidia.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
mfd@lists.linux.dev, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
linux-sound@vger.kernel.org, linux-tegra@vger.kernel.org,
Thierry Reding <treding@nvidia.com>
Subject: Re: [PATCH v3 2/3] dt-bindings: ASoC: nvidia,tegra30-ahub: Convert to json-schema
Date: Wed, 7 Oct 2026 16:10:15 -0500 [thread overview]
Message-ID: <20261007211015.GA305857-robh@kernel.org> (raw)
In-Reply-To: <20261002-as3722-bindings-v3-2-21c179b72a95@nvidia.com>
On Fri, Oct 02, 2026 at 09:38:59AM +0200, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Convert Tegra AHUB bindings from the free-form text format to
> json-schema.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> Rob, you gave a reviewed-by on v2, but Sashiko flagged that the per-SoC
> constraints don't properly match on Tegra132. The only change (well, in
> addition to the subject prefix fixup) compared to v2 is changing the
BTW, It's 'ASoC: dt-bindings: ...' that Mark is looking for.
Rob
next prev parent reply other threads:[~2026-10-07 21:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 7:38 [PATCH v3 0/3] arm64: tegra: Fix DT validation issues for Tegra132 Thierry Reding
2026-10-02 7:38 ` [PATCH v3 1/3] dt-bindings: mfd: as3722: Convert to json-schema Thierry Reding
2026-10-02 9:14 ` sashiko-bot
2026-10-02 7:38 ` [PATCH v3 2/3] dt-bindings: ASoC: nvidia,tegra30-ahub: " Thierry Reding
2026-10-02 9:14 ` sashiko-bot
2026-10-07 21:10 ` Rob Herring [this message]
2026-10-07 21:10 ` Rob Herring (Arm)
2026-10-02 7:39 ` [PATCH v3 3/3] arm64: tegra: Add Tegra132 specific compatible for AHUB Thierry Reding
2026-10-02 9:14 ` sashiko-bot
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=20261007211015.GA305857-robh@kernel.org \
--to=robh@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=ldewangan@nvidia.com \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mfd@lists.linux.dev \
--cc=thierry.reding@gmail.com \
--cc=thierry.reding@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