From: Mark Brown <broonie@kernel.org>
To: Sheetal <sheetal@nvidia.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Thierry Reding <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Mohan Kumar <mkumard@nvidia.com>,
Sameer Pujar <spujar@nvidia.com>,
linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
Anupama Kunkulagunta <akunkulagunt@nvidia.com>
Subject: Re: [PATCH 1/2] dt-bindings: sound: Add Tegra268 AHUB support
Date: Thu, 5 Nov 2026 00:21:55 +0000 [thread overview]
Message-ID: <eb487bb8-1d43-473b-8eac-c35f11aee6dd@sirena.org.uk> (raw)
In-Reply-To: <20261104112055.1101243-2-sheetal@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
On Wed, Nov 04, 2026 at 11:20:54AM +0000, Sheetal wrote:
> From: Anupama Kunkulagunta <akunkulagunt@nvidia.com>
>
> Tegra268 AHUB supports five RX and five TX ADMAIF interfaces, five
> I2S instances, two MVC instances, and one instance each of AMX, ADX,
> MIXER and ASRC.
Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resemble what they're doing.
There's no need to resubmit to fix this alone.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-11-05 0:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 11:20 [PATCH 0/2] ASoC: tegra: " Sheetal
2026-11-04 11:20 ` [PATCH 1/2] dt-bindings: sound: " Sheetal
2026-11-05 0:21 ` Mark Brown [this message]
2026-11-04 11:20 ` [PATCH 2/2] ASoC: tegra: AHUB: Add Tegra268 support Sheetal
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=eb487bb8-1d43-473b-8eac-c35f11aee6dd@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akunkulagunt@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@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=mkumard@nvidia.com \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=sheetal@nvidia.com \
--cc=spujar@nvidia.com \
--cc=thierry.reding@kernel.org \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®