From: Mark Brown <broonie@kernel.org>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
lgirdwood@gmail.com, "Sheetal ." <sheetal@nvidia.com>
Cc: perex@perex.cz, tiwai@suse.com, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-sound@vger.kernel.org, thierry.reding@gmail.com,
jonathanh@nvidia.com, spujar@nvidia.com, mkumard@nvidia.com
Subject: Re: [PATCH v3 00/11] Add Tegra264 support in AHUB drivers
Date: Thu, 22 May 2025 15:22:27 +0100 [thread overview]
Message-ID: <174792374755.97913.2208583690041067416.b4-ty@kernel.org> (raw)
In-Reply-To: <20250512051747.1026770-1-sheetal@nvidia.com>
On Mon, 12 May 2025 05:17:36 +0000, Sheetal . wrote:
> The patch series includes the necessary changes to enable
> support for the Tegra264 platforms in AHUB drivers.
>
> Changelog
> =========
> v2 -> v3:
> --------
> - Patch 1/11: Update commit message and update binding doc with info
> that the properties are not relevant for Tegra210.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[01/11] dt-bindings: ASoC: admaif: Add missing properties
commit: 37240f703041439cd8a39abd670dbfc0e75b725c
[02/11] dt-bindings: ASoC: Document Tegra264 APE support
commit: 628dafc476eb658544ad6b5b3592bfcd82597051
[03/11] ASoC: tegra: CIF: Add Tegra264 support
commit: 35c0d1de8e669878797e40cc625f4bdc37c3e084
[04/11] ASoC: tegra: ADMAIF: Add Tegra264 support
commit: 7668c6378b0577893bcf8c0f272b6ed099e0787d
[05/11] ASoC: tegra: ASRC: Update ARAM address
commit: fa83757df3f40c05b5ab4154253e8aeefa31a9a6
[06/11] ASoC: tegra: Update PLL rate for Tegra264
commit: 1fb500476f609008ee1c499540af32c4fa5a19de
[07/11] ASoC: tegra: I2S: Add Tegra264 support
commit: b3354438d89867654b4a95a9630fd3393e275e33
[08/11] ASoC: tegra: AMX: Add Tegra264 support
commit: fd509c6f8e4028539bf35d80e3bcdce7b3ba0f9f
[09/11] ASoC: tegra: ADX: Add Tegra264 support
commit: 7dc8299fbb1c8e6373e8e55d562b7674ee37b2b0
[10/11] ASoC: tegra: AHUB: Add Tegra264 support
commit: 4152d33ab162d5378f57cd757e1de5cb4867dfb4
[11/11] ASoC: tegra: Tegra264 support in isomgr_bw
commit: 7d852b34be4df61ae4327b47c39701d0f7ffcc70
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2025-05-22 14:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 5:17 Sheetal .
2025-05-12 5:17 ` [PATCH v3 01/11] dt-bindings: ASoC: admaif: Add missing properties Sheetal .
2025-05-14 21:46 ` Rob Herring (Arm)
2025-05-22 14:25 ` Krzysztof Kozlowski
2025-05-22 16:05 ` Sheetal .
2025-05-12 5:17 ` [PATCH v3 02/11] dt-bindings: ASoC: Document Tegra264 APE support Sheetal .
2025-05-12 5:17 ` [PATCH v3 03/11] ASoC: tegra: CIF: Add Tegra264 support Sheetal .
2025-05-12 5:17 ` [PATCH v3 04/11] ASoC: tegra: ADMAIF: " Sheetal .
2025-05-12 5:17 ` [PATCH v3 05/11] ASoC: tegra: ASRC: Update ARAM address Sheetal .
2025-05-12 5:17 ` [PATCH v3 06/11] ASoC: tegra: Update PLL rate for Tegra264 Sheetal .
2025-05-12 5:17 ` [PATCH v3 07/11] ASoC: tegra: I2S: Add Tegra264 support Sheetal .
2025-05-12 5:17 ` [PATCH v3 08/11] ASoC: tegra: AMX: " Sheetal .
2025-05-12 5:17 ` [PATCH v3 09/11] ASoC: tegra: ADX: " Sheetal .
2025-05-12 5:17 ` [PATCH v3 10/11] ASoC: tegra: AHUB: " Sheetal .
2025-05-12 5:17 ` [PATCH v3 11/11] ASoC: tegra: Tegra264 support in isomgr_bw Sheetal .
2025-05-22 14:22 ` Mark Brown [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=174792374755.97913.2208583690041067416.b4-ty@kernel.org \
--to=broonie@kernel.org \
--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@gmail.com \
--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®