linux-kernel - Re: [PATCH v2 1/2] ASoC: soc-component: add snd_soc_component_read/write

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <161176762855.34530.6617138298808888904.b4-ty@kernel.org>
Date:   Wed, 27 Jan 2021 17:13:48 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc:     tiwai@...e.com, alsa-devel@...a-project.org, lgirdwood@...il.com,
        vkoul@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/2] ASoC: soc-component: add snd_soc_component_read/write_field()

On Tue, 26 Jan 2021 17:17:48 +0000, Srinivas Kandagatla wrote:
> It's often the case that we would write or read a particular field
> in register. With the current soc_component apis, reading a particular
> field in register would involve first read the register and then
> perform shift operations.
> 
> Ex:
> to read from a field mask of 0xf0
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: soc-component: add snd_soc_component_read/write_field()
      commit: 1da0b9899abdbc7103d3ec6b1a888efda41dbb59
[2/2] ASoC: codecs: lpass-wsa-macro: make use of snd_soc_component_read_field()
      commit: 7db4c4cd767e5c2418e7892c6b2f06982d34369a

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