linux-kernel - Re: [PATCH v2 0/2] ASoC: ti: j721e-evm: Support for j7200 variant

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] [day] [month] [year] [list]

Date:   Mon, 14 Sep 2020 15:51:15 +0100
From:   Mark Brown <broonie@...nel.org>
To:     robh+dt@...nel.org, Peter Ujfalusi <peter.ujfalusi@...com>,
        lgirdwood@...il.com
Cc:     devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        alsa-devel@...a-project.org
Subject: Re: [PATCH v2 0/2] ASoC: ti: j721e-evm: Support for j7200 variant

On Thu, 10 Sep 2020 15:41:08 +0300, Peter Ujfalusi wrote:
> Changes since v1:
> - Suffix the 2359296000 constant with 'u' to silence C90 warning
> 
> When j7200 SOM is connected to the CPB, the audio setup is a bit different:
> Only 48KHz family have clock path, 44.1KHz is not supported.
> 
> Update the binding documentation and add support for the j7200 version of CPB
> to the driver.
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: dt-bindings: ti, j721e-cpb-audio: Document support for j7200-cpb
      commit: 18790b1b514a202bae2863a4206b731d95302c85
[2/2] ASoC: ti: j721e-evm: Add support for j7200-cpb audio
      commit: 18c140f4a2de8fa674d52fe522a47133bc124f81

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