Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
From:   Mark Brown <broonie@kernel.org>
To:     spujar@nvidia.com, lgirdwood@gmail.com, robh+dt@kernel.org,
        tiwai@suse.com, thierry.reding@gmail.com, krzk+dt@kernel.org,
        perex@perex.cz
Cc:     linux-tegra@vger.kernel.org, jonathanh@nvidia.com, will@kernel.org,
        catalin.marinas@arm.com, linux-kernel@vger.kernel.org,
        linux-arm-kernel@lists.infradead.org, alsa-devel@alsa-project.org,
        devicetree@vger.kernel.org
In-Reply-To: <1648735412-32220-1-git-send-email-spujar@nvidia.com>
References: <1648735412-32220-1-git-send-email-spujar@nvidia.com>
Subject: Re: (subset) [PATCH v2 0/6] ASRC support on Tegra186 and later
Message-Id: <164915109452.276574.5258971838741299202.b4-ty@kernel.org>
Date:   Tue, 05 Apr 2022 10:31:34 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Thu, 31 Mar 2022 19:33:26 +0530, Sameer Pujar wrote:
> This series adds support for Asynchronous Sample Rate Converter (ASRC)
> module on Tegra186 and later generations of SoCs. ASRC is a client of
> AHUB. The driver and DT support is added to make it work with Tegra
> audio graph card. The module can be plugged into audio path using ALSA
> mixer controls.
> 
> ASRC supports two modes of operation, where it gets the ratio info
> from SW and ratio detector module. Presently the support is added for
> SW mode.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/6] ASoC: tegra: Add binding doc for ASRC module
      commit: c54ce1a17232215c4a518149292b41835992eee8
[2/6] ASoC: tegra: Add Tegra186 based ASRC driver
      commit: a2df8c2d5b36fc66b9a6e674f3e0c87c0b9d0a48
[3/6] ASoC: tegra: AHUB routes for ASRC module
      commit: 76821c139d7e0429845e7c0798747e7eec16ec83

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