linux-kernel - Re: [PATCH v5 00/11] Add ASoC AHUB components for Tegra210 and later

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <159537940424.49432.12585025490958205269.b4-ty@kernel.org>
Date:   Wed, 22 Jul 2020 01:56:49 +0100
From:   Mark Brown <broonie@...nel.org>
To:     kuninori.morimoto.gx@...esas.com, tiwai@...e.com,
        robh+dt@...nel.org, perex@...ex.cz,
        Sameer Pujar <spujar@...dia.com>, lgirdwood@...il.com
Cc:     linux-kernel@...r.kernel.org, nicoleotsuka@...il.com,
        sharadg@...dia.com, thierry.reding@...il.com, jonathanh@...dia.com,
        atalambedu@...dia.com, linux-tegra@...r.kernel.org,
        mkumard@...dia.com, alsa-devel@...a-project.org,
        dramesh@...dia.com, nwartikar@...dia.com, digetx@...il.com,
        viswanathl@...dia.com, swarren@...dia.com, rlokhande@...dia.com
Subject: Re: [PATCH v5 00/11] Add ASoC AHUB components for Tegra210 and later

On Sun, 19 Jul 2020 10:31:19 +0530, Sameer Pujar wrote:
> Overview
> ========
> Audio Processing Engine (APE) comprises of Audio DMA (ADMA) and Audio
> Hub (AHUB) unit. AHUB is a collection of hardware accelerators for audio
> pre-processing and post-processing. It also includes a programmable full
> crossbar for routing audio data across these accelerators.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: tegra: Add Tegra210 based ADMAIF driver
      commit: f74028e159bb8e1de840d945af344bf93b59ada2

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