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]

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

Hi Mark,

On 7/20/2020 8:08 PM, Mark Brown wrote:
> External email: Use caution opening links or attachments
>
>
> 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/6] ASoC: dt-bindings: tegra: Add DT bindings for Tegra210
>        commit: 665308c0b44a37339b9b3368f1dd61eb66acde87
> [2/6] ASoC: tegra: Add support for CIF programming
>        commit: 1c3b89fb7e4a78ddcd627e3f218a216e2136ae9b
> [3/6] ASoC: tegra: Add Tegra210 based DMIC driver
>        commit: 8c8ff982e9e2b2eb9255fc393f938915b0ddc127
> [4/6] ASoC: tegra: Add Tegra210 based I2S driver
>        commit: c0bfa98349d1796fe754dfac7f7f505bb60dcd83
> [5/6] ASoC: tegra: Add Tegra210 based AHUB driver
>        commit: 16e1bcc2caf446fa3e1daa040b59fd6f6272a766
> [6/6] ASoC: tegra: Add Tegra186 based DSPK driver
>        commit: 327ef64702668bb754eeea80ce402454d7a1302a

I see that "[PATCH v5 07/11] ASoC: tegra: Add Tegra210 based ADMAIF 
driver" is not applied as part of this. I wanted to understand if this 
is because some more review comments are expected or there are other 
reasons?

Thanks,
Sameer.

>
> 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