linux-kernel - Re: [PATCH] ASoC: soc-utils: Improve kerneldoc for snd_soc_tdm_params_to

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: <166060132881.914979.11863568776659530881.b4-ty@kernel.org>
Date:   Mon, 15 Aug 2022 23:08:48 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc:     alsa-devel@...a-project.org, patches@...nsource.cirrus.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: soc-utils: Improve kerneldoc for snd_soc_tdm_params_to_bclk()

On Mon, 15 Aug 2022 12:33:46 +0100, Richard Fitzgerald wrote:
> The statement that snd_soc_tdm_params_to_bclk() is equivalent to
> snd_soc_params_to_bclk() if tdm_width==tdm_slots==0 is not accurate,
> it is only true is slot_multiple is also <2.
> 
> However, the description of special-case behaviour in terms of pairs of
> tdm_width and tdm_slot values is not particularly helpful so we might as
> well take the opportunity to rework the description to say the same thing
> in a simpler way. The behaviour of a pair of values is obvious from a
> description of each argument. At the same time make a few edits to clarify
> the rest of the description.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: soc-utils: Improve kerneldoc for snd_soc_tdm_params_to_bclk()
      commit: efe30e2cb6ff87467389cece8ce604f6601059f9

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