From: Thierry Reding <thierry.reding@kernel.org>
To: Sumit Gupta <sumitg@nvidia.com>
Cc: 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, bbasu@nvidia.com
Subject: Re: [PATCH v2 0/2] soc/tegra: cbb: Add Tegra238 support
Date: Fri, 27 Mar 2026 15:27:08 +0100 [thread overview]
Message-ID: <acaTo8UpTACvjO-3@orome> (raw)
In-Reply-To: <20260325125726.2694144-1-sumitg@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
On Wed, Mar 25, 2026 at 06:27:24PM +0530, Sumit Gupta wrote:
> Add support for Control Backbone (CBB) 2.0 based fabrics in Tegra238 SoC.
>
> The series includes:
> - DT binding updates for Tegra238 CBB compatible strings
> - Driver support for Tegra238 AON, APE, BPMP, and CBB fabrics
>
> v1[1] -> v2:
> - Add DT maintainers for review. Forgot to add earlier.
>
> Sumit Gupta (2):
> dt-bindings: arm: tegra: Add Tegra238 CBB compatible strings
> soc/tegra: cbb: Add support for CBB fabrics in Tegra238
>
> .../arm/tegra/nvidia,tegra234-cbb.yaml | 4 +
> drivers/soc/tegra/cbb/tegra234-cbb.c | 134 ++++++++++++++++++
> 2 files changed, 138 insertions(+)
>
> [1] https://lore.kernel.org/lkml/20260303155927.1885297-1-sumitg@nvidia.com/
Applied after adjusting the commit message as suggested by Krzysztof.
Thanks,
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-03-27 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 12:57 [PATCH v2 0/2] soc/tegra: cbb: Add Tegra238 support Sumit Gupta
2026-03-25 12:57 ` [PATCH v2 1/2] dt-bindings: arm: tegra: Add Tegra238 CBB compatible strings Sumit Gupta
2026-03-27 7:26 ` Krzysztof Kozlowski
2026-03-25 12:57 ` [PATCH v2 2/2] soc/tegra: cbb: Add support for CBB fabrics in Tegra238 Sumit Gupta
2026-03-27 14:27 ` Thierry Reding [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=acaTo8UpTACvjO-3@orome \
--to=thierry.reding@kernel.org \
--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=sumitg@nvidia.com \
--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