linux-kernel - Re: (subset) [PATCH 00/11] ASoC: cleanups and improvements for jz4740-i2s

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:   Thu, 07 Jul 2022 14:54:05 +0100
From:   Mark Brown <broonie@...nel.org>
To:     paul@...pouillou.net, aidanmacdonald.0x0@...il.com, tiwai@...e.com,
        lgirdwood@...il.com, perex@...ex.cz
Cc:     linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org,
        alsa-devel@...a-project.org
Subject: Re: (subset) [PATCH 00/11] ASoC: cleanups and improvements for jz4740-i2s

On Wed, 6 Jul 2022 22:13:19 +0100, Aidan MacDonald wrote:
> This series is a preparatory cleanup of the jz4740-i2s driver before
> adding support for a new SoC. The last two patches lift unnecessary
> restrictions on sample rates and formats -- the existing ones appear
> to be derived from the limitations of the JZ4740's internal codec and
> don't reflect the actual capabilities of the I2S controller.
> 
> I'm unable to test the series on any JZ47xx SoCs, but I have tested
> on an X1000 (which is the SoC I'll be adding in a followup series).
> 
> [...]

Applied to

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

Thanks!

[01/11] ASoC: jz4740-i2s: Remove Open Firmware dependency
        commit: 98356c89d44dac838dfbab02975645d828de3099
[02/11] ASoC: jz4740-i2s: Refactor DMA channel setup
        commit: 8a7691010992886290b340a1ba943067c2e70f85

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