[v2] ASoC: sophgo: cv1800b: document DAC overwrite handling

[PATCH v2 0/2] ASoC: sophgo: cv1800b: document DAC overwrite handling

Posted by Anton D. Stavinskii 1 week, 3 days ago

An incremental patch on top of 
"[PATCH v4 5/6] ASoC: sophgo: add CV1800B internal DAC" 
adding the explanatory comments as requested.
https://lore.kernel.org/all/20260120-cv1800b-i2s-driver-v4-0-6ef787dc6426@gmail.com/

changes: 
 - added description for cv1800b_dac_mute function
 - fixed "extra change" from previos commit

Thanks

Signed-off-by: Anton D. Stavinskii <stavinsky@gmail.com>
---
Changes in v2:
- missing Signed-off-by for the commit. 
- Link to v1: https://lore.kernel.org/r/20260127-incremental-for-i2s-dvier-v1-0-431b809c632d@gmail.com

---
Anton D. Stavinskii (2):
      ASoC: sophgo: cv1800b: document DAC overwrite handling
      ASoC: sophgo: cv1800b: tidy Kconfig spacing

 sound/soc/sophgo/Kconfig             | 1 +
 sound/soc/sophgo/cv1800b-sound-dac.c | 6 +++++-
 2 files changed, 6 insertions(+), 1 deletion(-)
---
base-commit: bdc79da6c6206a12c9a13ed5e4eb1360d62b321e
change-id: 20260127-incremental-for-i2s-dvier-9ec60a002bdd

Best regards,
-- 
Anton D. Stavinskii <stavinsky@gmail.com>

Re: [PATCH v2 0/2] ASoC: sophgo: cv1800b: document DAC overwrite handling

Posted by Mark Brown 1 week, 3 days ago

On Tue, 27 Jan 2026 23:08:18 +0400, Anton D. Stavinskii wrote:
> An incremental patch on top of
> "[PATCH v4 5/6] ASoC: sophgo: add CV1800B internal DAC"
> adding the explanatory comments as requested.
> https://lore.kernel.org/all/20260120-cv1800b-i2s-driver-v4-0-6ef787dc6426@gmail.com/
> 
> changes:
>  - added description for cv1800b_dac_mute function
>  - fixed "extra change" from previos commit
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: sophgo: cv1800b: document DAC overwrite handling
      commit: a8e3e488293118b8fa5d5e7ca786ca25b954ce12
[2/2] ASoC: sophgo: cv1800b: tidy Kconfig spacing
      commit: 8cf19b19dba8814ccc8b1179dabf28b7f8eefc22

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