linux-kernel - Re: [PATCH 0/5] ASoC: cs42l42: Some small code improvements

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]

Message-Id: <166075594756.566556.10171156201538682053.b4-ty@kernel.org>
Date:   Wed, 17 Aug 2022 18:05:47 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc:     linux-kernel@...r.kernel.org, patches@...nsource.cirrus.com,
        alsa-devel@...a-project.org
Subject: Re: [PATCH 0/5] ASoC: cs42l42: Some small code improvements

On Wed, 17 Aug 2022 13:23:42 +0100, Richard Fitzgerald wrote:
> This is a collection of minor improvements to the code or comments.
> 
> Richard Fitzgerald (5):
>   ASoC: cs42l42: Don't include kernel.h
>   ASoC: cs42l42: Add include dependencies to cs42l42.h
>   ASoC: cs42l42: Move cs42l42_supply_names to .c file
>   ASoC: cs42l42: Fix comment typo in cs42l42_slow_start_put()
>   ASoC: cs42l42: Use snd_soc_tdm_params_to_bclk()
> 
> [...]

Applied to

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

Thanks!

[1/5] ASoC: cs42l42: Don't include kernel.h
      commit: 8ccaa7eb76742579864ddf834a8ea9c036c2cc5a
[2/5] ASoC: cs42l42: Add include dependencies to cs42l42.h
      commit: b48d1da00fc8f32f7f75b8a34eb484f08b39ffaa
[3/5] ASoC: cs42l42: Move cs42l42_supply_names to .c file
      commit: dbd231732c99e336c2ece4a70896139e7f5a51a7
[4/5] ASoC: cs42l42: Fix comment typo in cs42l42_slow_start_put()
      commit: db568aab37c1af80057c12c97e6af049495c3e4a
[5/5] ASoC: cs42l42: Use snd_soc_tdm_params_to_bclk()
      commit: c2683ecfd1850cc99829691b2e1d90f1a6d75b8b

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