linux-kernel - Re: [PATCH 0/4] ASoC: cs35l56: Updates for B0 silicon

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:   Tue, 18 Apr 2023 19:09:01 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        patches@...nsource.cirrus.com
Subject: Re: [PATCH 0/4] ASoC: cs35l56: Updates for B0 silicon

On Tue, 18 Apr 2023 15:43:05 +0100, Richard Fitzgerald wrote:
> These patches make some small changes to align with the B0
> silicon revision.
> 
> Richard Fitzgerald (4):
>   ASoC: cs35l56: Update comment on masking of EINT20 interrupts
>   ASoC: cs35l56: Remove SDW1 TX5 and TX6
>   ASoC: cs35l56: Remove SDW2RX1 mixer source
>   ASoC: cs35l56: Rename mixer source defines for SoundWire DP1
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: cs35l56: Update comment on masking of EINT20 interrupts
      commit: 16e5fc8ae793947d7dd0de63c7a613798f75c237
[2/4] ASoC: cs35l56: Remove SDW1 TX5 and TX6
      commit: 5ab28c78a125a724684958f4caf8210127d3f528
[3/4] ASoC: cs35l56: Remove SDW2RX1 mixer source
      commit: d3a4efb334e5f6cbb3f2741fa07a873a2a78b016
[4/4] ASoC: cs35l56: Rename mixer source defines for SoundWire DP1
      commit: d29a966b72fb370128096393961f2c456ff24e3d

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